R
Rob Fitzpatrick
Guest
Hi Joel, You didn't mention your OpenEdge or OS versions, which may be relevant with this question. I tried your code; here are some average run times in ms with different DLCs on Windows (all GUI): 11.6 32-bit: 570 11.6 64-bit: 765 11.7 32-bit: 555 11.7 64-bit: 750 12.0 64-bit: 690 I ran it in a few recent 64-bit CHUI clients on a couple of different Linux boxes and it was in the 900s to 1300s. My PC is an old gen-3 Core i7 at 3.4 GHz; Win7, if it matters. I don't know much about the Linux boxes, as they are VMs on some host with specs, provisioning, and workload that I can't see. I tried it in 11.7 32-bit CHUI on Win10 (1903) on a gen-1 Core i7 2.67 GHz and it took about 36000 ms. Same box, 11.6 64-bit CHUI, about 37000 ms. Same box, 11.7 64-bit GUI, about 1030 ms. Same box, 11.7 32-bit GUI, about 915 ms. Tried it in 11.7 64-bit and 12.0 64-bit GUI on Win10 (20H1) on a gen-6 U-series Core i5 2.4 GHz and it was around 560 ms. Same box, 11.7 64-bit CHUI, about 187000 ms. During that time, both _progres.exe and its conhost.exe show heavy kernel-mode CPU activity. Granted, this isn't scientific testing. But clearly the run time depends on more than just CPU type and speed, given the significant variances I saw in some cases. I hope Progress can take up this testing and get to the bottom of it. It is a concern for sure.
Continue reading...
Continue reading...