I
Irfan
Guest
David, We regularly run tests on various clients including Windows system with a .NET OpenClient, looking for client response times. The testing’s goals are to identify internal locations that slow the client response times. For example: this test’s OpenClient makes a APSV call and returns back a JSON as a longchar. The server creates a copy of each record of a customer table to a temp-table and at the end we write that the datasets to a longchar. Attached the dotnet client and ABL program. For this test the default PASOE configuration was changed to run: 1 multi-Session Agent; execute up to 200 concurrent ABL requests. The conf/openedge.properties settings used in this test appear after the chart. When running the test on one of our internal 2CPU Windows boxes, the results are as below. (NOTE: the results will vary based on the kind of system you are running or kind of ABL code you are running). The %DIFF in RED means that PASOE has a slower client response time than a Classic AppServer; in GREEN show faster; in BLUE shows almost equal response time than a classic AppServer. Windows test - 2 CPU machine(Average Execution time in millisec) PASOE Clients %DIFF 1Client 91 86.6 5.08% 5Clients 427 443 -3.61% 10Clients 904 1021 -11.46% 15Clients 1413 1411 0.14% This test’s response is pretty typical and shows running PASOE with one client does not represent the optimizations gained by its multi-threaded and multi-Session architectures. maxABLSessionsPerAgent=200 maxAgents=1 minAgents=1 maxConnectionsPerAgent=200 numInitialAgents=1 maxSessionsPerAgent=200
Continue reading...
Continue reading...