Can anyone tell me what kind of response or user load I could reliably expect to get out of JRun given the following information: -Machine is a dual-processor PIII 500 w/512 Mg RAM running NT server. -JRun 3.0 sp2 -Nature of the app is this - a jsp page serves up a stateful session EJB to each user coming in; this stateful EJB makes use of a stateless EJB which provides a telnet connection to a legacy datasource from a pool of available connections. The telnet gives us XML data which is XSLT processed into HTML results. What we see is this in our benchmarking, a) if we lower the number of users and increase the number of transactions per minute, less threads are created by JRun (the java process) and we get good performance (less context switching) but we hammer the telnet connections and they end up throwing exceptions; or b) if we increase the number of users and decrease the number of transactions per minutes, more threads get created by JRun and we get poor performance because of extensive context switching (for 200 users coming in, JRun creates almost 300 threads). We know that a lot of our time is spend in XSL processing, mainly because we're currently using Xalan/Xerces, which are apparently the slowest. We'll try using something faster, but in the meantime, I'm just trying to get an idea for what we could expect to see in performance for what we've currently got. Any help/suggestions/ideas etc. are appreciated!! TIA, Robert ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
