Hi,
Running PB 2019 build 2170 on win 2008 R2, win 2012 R2 and win 2016, remote Console.
Is there any known solution to speed differences between Win 2008 R2 and Win 2012 R2 and win 2016.
We find that in 2008 R2 remote Console, data in the datawindow is updated significantly faster than 2012 and 2016.
When running data extract form Oracle 12.2 of approx. 58,000 rows with 72 columns then 2008 R2 deliver in around 28 sec. (16 sec to run sql and 12 sec to fill data window complete).
In 2012 R2, however, the same run takes around 60 seconds. (same 16 to sql but 44 sec to fill data window with all rows).
We can't see any differences, so our question is if there could be anyone knowing of any solutions to fix it, or do we just have to live with it as is.
We also try running RDP on Win 2008 and got same speed as on 2012 and 2016 (60 sek).
We discover tha by putting another window (command window or other) over the PB datawindow (datawindow behind the command window).
RDP deliver same speed as the run on Remote Console in 2008 R2. (less than 28 sek.)
This trick do not work in 2012 or 2016. Neigther in 2019.
A good idea, anyone ?
With regards
Ivan Aase
1) PB is 32 bit
2) compile with P-Code
regards .. Ivan.
Thank you for that extra information. I do not personally have much "words of wisdom" as to this change in behaviour but, now that we have your particulars, maybe someone who has used those same MS-Windows O/S's can "chime in" here with some of their observations.
In the mean time, one thing for sure that can slow any PB App down when deployed into these environments is the "default printer" as PB's DW run--time engine renders the DWO as a bitmap and derives the fonts for that rendering from the default printer. So changing the default printer can have a significant impact on PB App performance.
The other thing that I am always leery about is the Anti-Virus being used and/or its settings that can hamper the performance because its always monitoring & scanning every work file.
Food for thought - HTH
Regards ... Chris