One single session, being absolutely the only user process connected to your computer, can load your CPU up to 100% for a long time very easily.
On the other hand you could have thousands of users connected on that same CPU (provided you have *a lot* of physical memory available) and the CPU will be idle for most of the time, if those sessions are only connected and don't do anything.
It's not the number of sessions that load the CPU, it is what those sessions are doing...
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Originally posted by jmodic One single session, being absolutely the only user process connected to your computer, can load your CPU up to 100% for a long time very easily.
On the other hand you could have thousands of users connected on that same CPU (provided you have *a lot* of physical memory available) and the CPU will be idle for most of the time, if those sessions are only connected and don't do anything.
It's not the number of sessions that load the CPU, it is what those sessions are doing...
ok, then if it's a new application, the only way is to test it.
Thanks
Orca
Reply With Quote
Bookmarks