I
Irfan
Guest
Please find my comments below Okay, l misstated the memory consumption results. The memory averages were from a Multi-session Agent with 5 sessions and the combined memory of 5 Classic Agents after running the various tests (not at startup). Okay. Can you put down the amount of memory used by the resources for running Classic Appserver(Adminserver, nameserver, Appserver broker, number of agents) and then PASOE(Server and MS-Agent) Are you saying that a Multi-session agent with N sessions will consume less memory than the same number of Classic Agents or that in total PASOE should consume less memory because one might need fewer MS-Agent sessions than Classic Agents? If the latter, then wouldn't we would need to move away from using bound connections thus introducing the additional overhead of context management? I am referring to your first statement, which is Multi-session agent with N sessions will consume less memory than the same number of Classic Agents. In Classic each agent process gets started which holds some memory where as in MS-Agent only 1 Agent is used with a set of sessions. I also ran tests with 5 concurrent clients running on 5 different sessions and found the performance results to be the virtually the same Classic always outperformed PASOE. I'm not sure I understand how putting more load on will change the performance? I haven't ran with 5 concurrent clients earlier, I always used 25 or more. I will give it and try at my end and see what I get. May I know what your appserver code does Also, what are your Agent configurations for number of sessions and Agents Note: These are somewhat primitive tests with out-of-the-box tuning.
Continue reading...
Continue reading...