We're in the process of upgrading from Arev31 to Arev32/OI and thought that, after fixing the bugs, we would deploy Arev32 to our users until we get the system up to OI standards.

In doing so, we're experiencing that there is a lot of lag in terms of application responsiveness from Arev32 compared to Arev31 where a command that seemed to execute instantaneously in Arev31 takes a few seconds to do so in Arev32.

Additionally, in windows that we converted to Arev32, holding down the down arrow to scroll through fields faster leaves the cursor scrolling through more fields than we intended because of the aformentioned lag.

Is there any way to improve the responsiveness of the system so as to not completely frustrate our users when it comes time to deploy Arev32 to a group of people that have been using Arev31 and are used to its resposiveness?

Thanks.

Shem-

How are you launching Arev32? Are you using a local java engine, or one on the server?

Mike

Mike,

I have a shortcut that opens OI with the files located on the server. When I launch OI using this shortcut, only an OINSIGHT.exe process is shown in my Task Manager. When I launch the program while logged into the server via Remote Desktop, an OENGINE.exe process is also opened.

Shem, we have recently found an issue with AREV32 that when running in the production environment it slows down as windows are being opened and closed. We are addressing this today. Are you experiencing this slow down in production or is it slow as soon as you start up.

Bob,

I speak generally when I say that it's slower in performance compared to Arev31. We have yet to take into account opening numerous windows as being the cause of the slowdown, as the comparative performance difference is evident at the launch of Arev32. Please let me know if there's anything we can do.

Thanks.

I think you're seeing the slower screen updates rather an actual performance decrease.

The performance benchmarks I've done shows that the processing speeds are pretty much the same as OI32 vs ARev 16 bit.

It's like running ARev under XP in a windowed vs full screen mode. The windowed mode seems much slower because of the screen writes but it takes the same amount of time to run a sort select or to rebuild an index in either screen mode.

View this thread on the Works forum...