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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

large number of context switches & pagefaults

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
i have build a com+ application for a website (vb 6.0 , STA, ActiveX DLLs).

it works with several user classes wich use a so called payload class to make XML strings and converting them with XSL to HTML, sending them back to the asp page for output.

now, when i started stressing the application and it comes to around 150 concurrent users pagefaults increase to about 5-6000 per second and there are around 40000 context switches per second ==> webserver is at 100% ;)

i'm using CreateInstance for accessing the payload object from inside the user classes and the NEW keyword for ADODB stuff and MSXML (4.0).

is there some basic error in this concept or has anyone of you experienced similar behavior of an application (all dlls are registered in the com+ service manager) and most important: where is the root of this problem?

if anyone of you has some hints for me i'd be more than grateful, cause i've not discovered the bottleneck yet.

thanks in advanced,

thomas kay

P.S.: frequently visited pages are cached in application variables to free database resources (database and webserver are on two different servers, using MS win2k advanced server and SQL server 6.0)
 
Is your web server a Multiple Processor System?


DAS
 
Ok,
I experience a similar problem with a dual processor system using just com+ components, no asp.
My application it's working faster in a single processor than on a dual processor. Try setting process affinity to the dllhost to just one processor an see what happend.
I still can't fix it.

DAS
 
sorry for the delay, everything works fine now, left out a parameter for an applet and this darn thing called the index page 20 times per second ;))

now everything is fine and smooth at 10-15% cpu usage with 1000 concurrent users ;) caching xml rules!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top