Hi Jay,
I don’t see this problem.
Here is the output from the cygwin shell wrapping
the caget inside “date” commands. 13IDC:m2 is a PV on a
vxWorks IOC.
# date ;
/cygdrive/c/epics/base-3.14.11/bin/win32-x86/caget 13IDC:m2 ; date
Wed Feb 16 14:43:42 CST 2011
13IDC:m2
5000.1
Wed Feb 16 14:43:42 CST 2011
rivers@Rivers-Mobile ~
# date ;
/cygdrive/c/epics/base-3.14.11/bin/cygwin-x86/caget 13IDC:m2 ; date
Wed Feb 16 14:44:02 CST 2011
13IDC:m2
5000.1
Wed Feb 16 14:44:02 CST 2011
# date ; /cygdrive/c/Program\ Files/EPICS\ WIN32\
Extensions/caget 13IDC:m2 ; date
Wed Feb 16 14:46:22 CST 2011
13IDC:m2
5000.1
Wed Feb 16 14:46:22 CST 2011
So it is taking less than 1 second to run caget from
both the win32-x86 and cygwin-x86 architectures from base-3.14.11, and from the
EPICS Win32 Extensions version.
Mark
Hi
EPICS folks,
I’m running caget and caput utility functions from cygwin and DOS on a
Windows XP system to get and put data to a VxWorks IOC on the same subnet. I
would like to know if there is some option to help speed up the execution of
these utility functions. For both sets of utility functions, the majority of
the execution time (4-5 seconds) seems to be spent running the
ca_context_destroy function at the end. I don’t see this delay when
running caget and caput functions to get and put data to a Soft IOC running on
the same Windows XP computer. I don’t understand why there is such a
delay just to clean up at the end.
I’m using epics base v3-14-11 for cygwin and EPICS WIN32 Extensions
Version 1.40 (Build 40) for DOS.
Thanks,
Jay
Steele
Xradia
Corporation
The information in this email, including
any attachments, is confidential and intended only for the recipient(s) listed.
Any use of this email for any other purpose is prohibited. If you have received
this email in error, please notify me immediately by reply email, delete this
email, and do not disclose its contents to anyone.