[THIN] Re: thread quanta and chkroot.cmd thingy
- From: "Brian Madden" <brian@xxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 16 Sep 2003 10:41:43 -0400
Exactly.
That's my point. These 180ms or 30ms are simply limits. Think of them as
circuit breakers. Most threads operate for for less than that, probably even
far less than 10ms.
My point is that even the "small" limit of 30ms is so high that I'm sure no
thread in a TS environment ever hits that limit. This is why I think the
setting doesn't matter, since no thread would ever hit it.
Brian
Brian Madden
202.302.3657
brian@xxxxxxxxxxxxxxxx
--------
Visit www.brianmadden.com for thin client white papers, books, product
reviews, courseware, and training videos.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Andrew Rogers
Sent: Tuesday, September 16, 2003 10:21 AM
To: thin@xxxxxxxxxxxxx
Subject: [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
********************************************************
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:
