We are having trouble with the dll license checking when deploying.

When the dll checks the license automatically it takes up to 30ms during the checking process - this is 30ms that we don’t have or are not prepared for. If we use the manual checking feature we have to call the same dll, which holds up our threads in any case causing the same problem.
We cannot decrease our calls to the dll by increasing the number of samples, because this will cause us to fall to far behind on the process. We can also not decrease our sample size and fit the call to license check in between.

Is there perhaps a workaround? Or are we missing something?

Hi Hanz,

we have significantly increased the number of executions between the automatic license checks.
You can find the new builds of the library in your “customer center” page.

Please let us know if that solves your problem.

Pavel

Thanks, Pavel

Unfortunately any hang up at any stage will be bad for us. We will try it and see if it (the new build) helps, but somewhere along the line we will have to stop the process to check the license.

Isn’t it perhaps possible to have a separate dll/exe, lying in the memory and checking the license, that will interrupt the main dll if it cannot find the license? If we have a multicore machine we can run our time critical thread on a separate processor.

Hanz

Hi Hanz,

you can download the second build with workaround for your problem. It’s removing the repetitive license check from prsd_Execute. It’s only a short term solution - we’ll contact you to figure out better way to keep deterministic execution so we can include it in the public version.

Greetings,

Pavel