Originally posted by Alexis C. Montenegro
es5es5
There is an option to synchronize (on Data Manager startup only) the system clock to that of eSignal's network.
To enable/disable synchronization open Data Manager then in the main menu select Data->Time.
Alex
es5es5
There is an option to synchronize (on Data Manager startup only) the system clock to that of eSignal's network.
To enable/disable synchronization open Data Manager then in the main menu select Data->Time.
Alex
Thanks. I already have that turned on. But even with that turned on the clock goes out of sync when the cpu is saturated. The clock is eventually resynced as cpu usage fluctuates. I think the problem is that eSignal is dropping events and data from winros. The system is literally too busy for eSignal to accept any more data. (eSignal was the only non-system app running.)
I must point out that I haven't had any clock sync problems since upgrading my computer earlier this month, and I check several times daily. That, to me, says something inside eSignal is inefficient enough to require alot of cpu power to overcome.
I've been a programmer for 22 years and, to me, this looks like (at least partly) inefficient memory utilization -- almost as if thousands of small new and deletes (or object instantiation and destructions) were happening each second.
It would shed some light on this issue if we could somehow profile eSignal as it runs in our environment.
Thanks again for your message.
Comment