D
dbeavon
Guest
I'm not sure about PASOE. I've never gotten a chance to try it out yet. One thing I will say is that you should benchmark your performance on your appserver calls and get a good feel for how long they should be. The difference between ~60 ms and ~4 ms may not seem much, but when you multiply by x10 or x20 different round-trips - in order to display a variety of data to the user - it makes all the difference in the world between a snappy U/I and a sluggish one. I'd also suggest using the "process of elimination" - take the network out of the equation and connect from the same machine, or take PASOE out of the equation and run the same underlying code directly from the Progress editor... You get the idea... Then review your changes and your numbers to see if the performance increases between each of these scenarios seems reasonable. For me one thing I will *always* include in my troubleshooting is a step where I take the HP-UX platform out of the equation, and try the same OpenEdge repros on Windows. It doesn't pay to be running on a stale/legacy platform, no matter how "mature" or "reliable" people say it is. I think the best possible scenario is to use the *same* platform that the OE product development team is using to get their work done (ie. the platform where they are actually doing the work on the features and performance optimizations like "singleton" and "single-run"). Otherwise there is always a potential for stuff to be lost in translation during a port to another platform - especially in relation to non-trivial things like performance.
Continue reading...
Continue reading...