The OE database is apparently receiving a lot of performance improvements in OE12.
One thing that is still quite slow is the delay that is experienced in client/server apps when trying to lock a record that is already in use by another session. For example if two sessions are alternately locking and unlocking the same record, I think there is a mandatory wait time of about 1 second whenever the exclusive-control of the record is transitioned back and forth. The client/server ABL session won't be allowed to receive access to the record any faster than what is specified in the startup parameter (-Nmsgwait). Depending on the application or service, a wait time of a whole second for a single record can be significant.
(Of course, you can do some manual work to write the code in a way that uses NO-WAIT, but is fairly labor intensive and results in messy logic.)
Is there any change in OE 12's behavior? Progress brags about OE 12 being 300% faster, but there are *lots* of real-world factors that could cause us to see much less impressive performance gains. The -Nmsgwait parameter is one thing that would limit our gains. It can dramatically affect ABL code whenever there high record contention.
Any information would be appreciated. In the perfect world they would re-interpret that parameter (for OE 12 and above) to refer to milliseconds instead of seconds.