|
PureBytes Links
Trading Reference Links
|
as a simple solution do not open several workspaces at the same time,
but one by one and give the buffer few seconds time to unwind.
rgds hans
> Windows in it's various incarnations starting with 3.0 incorporated a
> "Yield" event which allowed a programmer to yield a long running task to
> the operating system so that the Os could allow other tasks to run. It did
> not take a rocket scientist to build apps which did not hog the CPU (as
> TS/SC does when loading) nor did it take a rocket scientist to simulate
> threading which allowed related tasks to proceed. Later versions of
> Windows have facilitated the building of truly threaded apps. Omega
> programs have been generally ill-behaved and in the social world would be
> considered selfish. Perhaps they will properly thread operations in TS5.
> In any event, more memory should reduce load time, alternatively a faster
> processor.
>
>
> Earl
>
> -----Original Message-----
> From: Peter2150@xxxxxxx <Peter2150@xxxxxxx>
> To: prestonm@xxxxxxxxxxx <prestonm@xxxxxxxxxxx>; omega-list@xxxxxxxxxx
> <omega-list@xxxxxxxxxx> Date: Friday, August 21, 1998 8:55 PM Subject: Re:
> data reception during LOAD WORKSPACE
>
>
> >No reason why TS 5.0 would correct it. Problem is when you load work
> >spaces the CPU is loaded down with that and the server can't process
> >data. The only option would be to slow down the workspace loading so it
> >wouldn't effect the server. Of course no telling how long the workspace
> >load would take. Clearly a faster computer will load the workspace faster
> >and thus lessen the effect.
>
>
|