I
Irfan
Guest
Hi Blake, Considering the fact of a Production environment which might have many concurrent clients connecting to the appserver with various loads, the kind of tests that we ran has of load of 25 concurrent clients running on 25 different sessions which has 25 connections under 1 Multi-session Agent. The payloads that we used for testing looks like this for each transport APSV – 400 KB for each Client( 100 temp-tables where each temp-table has around 200 fields) REST – 260 KB of json payload for each Client WEB - 2.7KB to 25KB of payload for each Client( ran for 25 and 50 concurrent clients) The multi-session agents takes up more memory at start-up, so if you compare the memory of 1 _proapsv process with another _mproapsv process then it might not be the right comparison. The comparison should be between "n" _proapsv processes vs 1 MS-Agent with "n" sessions, where "n" refers to the number of "Classic Agents/MS-Agent sessions" you want to use in the appserver. Again the same applies to the Classic Appserver broker and the PAS Server.One PAS Server has the ability to run various web-applications inside it, support all kinds of transports for both Session-free and Session-Managed applications, manager applications and others whereas if you need to do the same in Classic Appserver you have to do it by configuring many servers. So the initial memory loaded in the PAS looks bigger, but the resource utilization of it should be considered once you try to put a decent load on the server
Continue reading...
Continue reading...