Running Adobe Livecycle on M-Series

Question

All -
We've been having performance issues and stability issues running Adobe Livecycle ES2 on T-series;hence we're doing a POC on M-series. This came after finding out that Adobe LC is not meant to take advantage of the T-series architecture which is more suited for multi-threaded applications. So, as of today our testing on the m-series is looking good.
My concern is, and we're planning of using reader extensions and rights management, is when we expose this to many users.
Is there anyone running on m-series with more than 1000 users and how is that performing?
Welcome your feedback.
Thank you.
Eduardo
AFT, Allstate

Answer 1

Hi Lukasz,
So, the issue here is that you're monitoring the loop rate of your 1kHz timed loop. This loop is made so that it will execute every millisecond, but the DAQmx API are not deterministic function calls. So, because we can't guarantee their determinism, you will see your loop rate fluctuating. As long as your loop is exectuing every 1ms and you immediately  call the DAQmx Write function to update the output buffer, this is as close to a solid 1kHz update rate that you'll be able to acheive.
The issue that seems to be coming up with your loop execution rate that directly affects the CPU usage and replenishing of the buffer, is when the execution of the DAQmx VIs in the while loop cannot execute in under 1ms. This causes some delays in replenishing that buffer, which is why the buffer size is dipping and consequently means that the CPU has to work as hard as it can to execute those actions in an amount of time that will satisfy the timed loop. 
Another thing that is going to help with this issue, is allocating a larger buffer size than the 1k that you have. This will provide more wiggle room while writing new data to it.
I still think that keeping the event structure in this loop and leaving the "allow regeneration" on will help the performance of this execution because you will only update the buffer when the user (or accompany PID conditions) wants to change the duty cycle. And since the DAQmx API execution is not deterministic within the timed loops, your update rate should as good, if not better, than without the event structure.
Also, another option you have is to simply use a counter output task and only update the duty cycle of that counter output when the duty cycle changes. I would have a look at the two example programs that are available on our Developer Zone Community. Take a look HERE and HERE.
I hope that helps explain things and gives you good options.
Chris W