execution time for dpGet

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
4 posts • Page 1 of 1
eMichx
Posts:64
Joined: Thu Apr 24, 2014 11:24 am

execution time for dpGet

Post by eMichx »

Hello,

We use the dpGet function (multiple DP or not), and by measuring the execution time, we arrive at important times
which vary between 350ms and 1,2sec.
Sometimes a dpQuery is faster.
We work on a base of 23477 DPs (120442 original, 3996 _dp_fct) (DP_MSG_CONNECT: 83/83)
How can we reduce this execution time for dpGet function?

regards
Emmanuel

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: execution time for dpGet

Post by leoknipp »

Hello,

the "execution time" depends on several factors:
-- current load on the system
-- messages processed at the moment
- -tasks processed at the moment (backups, recovery, ...)
-- type of information read with a dpGet, if the message needs to be send from the event manager to another manager (data, drivers)
-- how the execution time is measured

There is no possibility to give an answer without detailed information.
E.g. if the event manager is working on answering a dpQuery message no other message is processed and therefore it can take longer until the answer for a dpGet is received.

Best Regards
Leopold Knipp
Senior Support Specialist

eMichx
Posts:64
Joined: Thu Apr 24, 2014 11:24 am

Re: execution time for dpGet

Post by eMichx »

Hello,

The system seems to be not loaded (see file joined). No recovery or backup task
I have realized several tests and the responses time were more or less equals (350ms 1,2s)

The execution is realized as following :
t0= getCurrentTime();
dpGet(xxx);
t1=getCurrentTime();
DebugN("TIME : " + formatTime("%X",t1-t0,".%03d"));


regadrs
Emmanuel https://www.winccoa.com/fileadmin/image ... emInfo.zip
Attachments
SystemInfo.zip
(1.22 MiB) Downloaded 206 times

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: execution time for dpGet

Post by leoknipp »

Hello,

with the information in the attachment we cannot see the current load for the system.
If you want to see the current message traffic you have to define an update interval at the panel for the "Event Manager Connections". Otherwise the information is not updated and does not reflect the current state of the system.
As written in my previous posting we need more detailed information, e.g. a message protocol for the event manager.

Is it critical in your project that the response time varies?
Why is it critical?

If you need further assistance please get in contact with your common WinCC OA support.

Best Regards
Leopold Knipp
Senior Support Specialist

4 posts • Page 1 of 1