[THIN] Re: thread quanta and chkroot.cmd thingy

Just to throw a spanner in the works.. following on from your logic, surely 
you'd want the slice to be small? 10 threads suddenly using their full 180ms 
quota could potentially be an almost 2s stall..? or have I missed something 
fundamental like I suspect? :)

Andrew
--o--

>>> brian@xxxxxxxxxxxxxxx 16/09/03 14:58:40 >>>
For example, if a thread was able to use its full 180ms time slice, only 5.5
threads would execute per second. Imagine you have a server with 50 users.
In order for each user to get access to the CPU at least once per second,
they would need to have threads execute for them for a maximum of 20ms. (1s
/ 50users = 0.02s each). This is well under even the 30ms limit as
configured by this setting. Then, on top of that, remember that each user
has multiple threads running, etc, and that they need access to the server
more than once per second. I guess my point is that in a Terminal Server
environment, I can't possibly imagine a single thread coming anywhere near
the time slice/quanta limit, whether the limit is 30ms, 60ms, or 180ms.


********************************************************
This Week's Sponsor:  ThinPrint
http://www.thinprint.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm

For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm

Other related posts: