At Progress Next this year there was a presentation I went to on why migrate to PASOE. In that session there were some caveats mentioned, one was that inefficient coding practices would be magnified under load, I've heard this from others at Progress as well. We are getting ready to migrate to PASOE, it would be nice to get any inefficient coding addressed before it becomes a problem in production. Does anyone have examples of inefficient coding practices that have caused performance issues when migrating to PASOE?
Thanks, Most of our customers are running the appservers on a UNIX machine. We will be state-free with the agent being self service, at least until the remote connection performance is better. We try to have as much r-code stay in memory as possible, large -mmax and -D parameters. We also use a local .pl for the code to minimize writing to the r-code swap file. Would those same parameters apply with PASOE?