Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Context switches/sec
- Thread starter ngreensa
- Start date
Neil, I took your question to one of our developers and this was his response. FYI - this developer was heavily involved in the coding of the Citrix RMS product (which was originally ours under the SysTrack 1.0 name).
His response:
"That looks mildly high to me. It’s hard to answer without knowing a lot of other things.
The context switch rate will vary more with the number of active threads than with the number of processors in the system. More active threads will necessitate more context switches, but more CPUs to run the threads will result in a lower per-processor rate (since they’ll share the load, and there will be less CPU contention). The context switch rate will also depend heavily on the nature of the application load. It’s actually a lot more complex than this, but perhaps this will help a bit…
If I was forced to guess without any other information being available, I’d say up to 9000 context switches per second on a uniprocessor terminal server is typical. Since the 14K is not radically higher, I’d guess that this is OK. But I would need much more data to be certain."
Was this helpful at all?
Mike
Kapski@yahoo.com
SysTrack 3.1 is available now!
His response:
"That looks mildly high to me. It’s hard to answer without knowing a lot of other things.
The context switch rate will vary more with the number of active threads than with the number of processors in the system. More active threads will necessitate more context switches, but more CPUs to run the threads will result in a lower per-processor rate (since they’ll share the load, and there will be less CPU contention). The context switch rate will also depend heavily on the nature of the application load. It’s actually a lot more complex than this, but perhaps this will help a bit…
If I was forced to guess without any other information being available, I’d say up to 9000 context switches per second on a uniprocessor terminal server is typical. Since the 14K is not radically higher, I’d guess that this is OK. But I would need much more data to be certain."
Was this helpful at all?
Mike
Kapski@yahoo.com
SysTrack 3.1 is available now!
- Thread starter
- #3
Hi mike
thanks for the input, i am actually getting +- 14k processors on a duel 2.4 Ghz Xeon server (compaq DL) with hyperthreading. Some of the servers are running up to 60,000 when under load. just curious i guess as there is not much documentation on this particular metric, i guess its down to baselining each individual server to see what it can handle
thanks
Neil
thanks for the input, i am actually getting +- 14k processors on a duel 2.4 Ghz Xeon server (compaq DL) with hyperthreading. Some of the servers are running up to 60,000 when under load. just curious i guess as there is not much documentation on this particular metric, i guess its down to baselining each individual server to see what it can handle
thanks
Neil
- Status
Similar threads
- Locked
- Question