We have determined the cause of the data delays in Pulse. The problem was in the client software (not the server) and has been fixed.

In order to make this fix available as soon as possible, we have decided to backport the main parts of it into a new 3.3.X release. Pulse 3.3.56 is now available and does not fall behind the market. It can be downloaded from:
http://www.paritech.com.au/paritech/support_PULSE.html

The upcoming release 3.4 of Pulse will include more CPU usage improvements in Pulse to even better handle high data loads.

For the technically minded, this problem was being caused by 2 main factors:
  • The data messages were being trapped in the lower levels of Pulse when many display changes were occurring. This was fixed by reorganising thread priorities in Pulse.
  • Idle processing was occurring very frequently due to the real time nature of Pulse. We are now more selective about when to allow idle processing.
Regards
Paul