D
dbeavon
Guest
I am emulating classic statefree appserver in PAS with a remote .Net openclient using the APSV transport. If I do some profiling with procmon, there appears to be 5ms overhead on the front end (when a request for a database record arrives) and also 5ms on the back when the ABL results are returned. The 5ms + 5ms overhead apears to be the local chat/cpu interaction between the tomcat (java.exe) process and it's OE agent (_mproapsv.exe). There is a remaining amount of time that consists of the work in the agent client/server code (ABL) that retrieves the record from a remote database. This work can take about 5ms since it uses a client/server protocol on the network. These are the very fastest possible round-trips I've seen so far out of the APSV transport (usually 15-20 ms as observed by remote openclient). In contrast, we had been getting fast 5-8 ms round-trips with classic statefree appserver clients. These small delays may not seem much, but if a complex U/I makes 10 or 100 round-trips to redraw a screen then it becomes a delay that can be certainly noticed by a user who is banging away on updating their data. Does this (~10 ms) overhead on the APSV sound right? Is there a faster transport that we might start looking into now that we are using PAS? Thanks in advance.
Continue reading...
Continue reading...