WinCC OA 3.14 / dpGet performance problem

[ozangor]

Greetings everyone,

While I was doing some tests by myself, I realized that there is a significant drop on the performance of dpGet function in the version 3.14.

I did a basic test:

Created new projects on both versions.

Created a panel that calls 1000 times dpGet on the same dpe and shows the start and end time of the loop.

The results were really sad:

For version 3.13 (with latest patches):

1000 Cycles
Elapsed Time: 1.049 seconds

For version 3.14:

1000 Cycles
Elapsed Time: 10.042 seconds

What might be the reason behind this? Is this because of the new types announced?

Best Regards,

Ozan


Edit:
OS: Windows 7 Enterprise/SP1 x64

[buec]

I did the same test. Here the result:

WinCC OA 3.14
["1000 dpGet dauern: 10.002 Sekunden"]
["1000 dpSet dauern: 00.007 Sekunden"]
["1000 dpSetWait dauern: 10.003 Sekunden"]
["1000 dpQuery dauern: 10.002 Sekunden"]

WinCC OA 3.13
["1000 dpGet dauern: 01.000 Sekunden"]
["1000 dpSet dauern: 00.004 Sekunden"]
["1000 dpSetWait dauern: 01.000 Sekunden"]
["1000 dpQuery dauern: 01.140 Sekunden"]

I attached my test Panel. (rename .txt to .xml to use it)

Hopefully there will be a patch soon...

Regards
Christoph

[buec]

Attachement: https://www.winccoa.com/fileadmin/image ... tDpGet.txt

[leoknipp]

Hello,

the difference between 3.13 and the newest version 3.14 is caused by changes for the user interface. For the CTRL manager no changes have been made.
We know that the behaviour of a single call of dpGet(), dpConnect(), ... has changed.

If several threads are running at the same time, e.g. during the initialization of several objects when opening a panel or during runtime when updates are received, you will not see any difference between 3.13 and 3.14.
In normal use cases a UI will have several threads running at the samee time. Therefore please check the performance of the UI in real conditions and not only with isolated calls of UI functions.

Best Regards
Leopold Knipp
Senior Support Specialist

[leoknipp]

Hello,

our developers have made additional changes in 3.14.
The changes will have an effect on the performance of dpGet(), dpConnect() to get the same performance as before.

With the next patch for 3.14 (planned for end of February 2016) the changes will be available.

Best Regards
Leopold Knipp
Senior Support Specialist