We’ve run into an issue where a Haystack connection is substantially raising the CPU usage on a Jace. The CPU is pegged at/near 100% whenever the Haystack connection is established. We’ve tried different combinations of Niagara 4.4, 4.7 and 4.9 with nHaystack 2.1.2 and 3.0.1 all with the same results (there is slightly less CPU usage on 4.4/2.1.2, but still greater than 90%)

• Here is the drop in CPU when the connection is disabled for all points: https://www.dropbox.com/s/3miays3de584tqf/Disabling%20the%20connector.JPG?dl=0
• Here is the rise in CPU when a single point is added to the connector (the connector was enabled prior to the rise): https://www.dropbox.com/s/mbwoqberie27a6g/Enabling%20a%20single%20point.JPG?dl=0

(These images are with 4.9 and 3.0.1)

Has anyone else run into a similar issue? Or have any idea of the cause?

Keith,

Call me since you have an environment that is in place. Let's enable spy log for these and check errors. If we can't see it, we might need to place log outs for the nhaystack. I will try to help. Also can you create a ticket on github as well.

Let's track it from here.

https://github.com/ci-richard-mcelhinney/nhaystack/issues

I have ran into high CPU Usage as well on JACEs with 2 or 3.0.1 with N4.4, 4.7, and 4.9. SoftJaces/Supervisors seem to have enough horsepower to deal with nHaystack queries from SkySpark, but on JACEs I usually resort to a process other than haystackReadAll(...) to build (either exporting portions of the system to csv, or building manually on small sites).

From what I could remember, it seemed like every time I initiated a query against the nHaystack driver, it caused a new login session with the JACE (something in how Tridium handles login sessions). Supposedly using an HTTP Basic Auth Scheme helps with this, but I didn't have much luck.

Would be curious to see the results of your guys investigation, and/or if you want to throw up your troubleshooting steps/what you modify for spy logging and maybe compare notes!

Hi Keith et al,

Just wanted to follow up on this. We are doing some work on nhaystack and some performance improvements have been identified. We are hoping to do a new release soon and these will be included.

I'll keep you posted.

Cheers, Richard

Hi Richard,

We are following developments on this issue as we have several J8000s experiencing heavy resource loading when the haystack service is activated.

If you have any progress updates, we are keen to hear them. Thank you.

Hi Keith and everyone following this topic.

I have just posted on the forum that a new version of nhaystack is available. There have been a number of performance improvements and I would very much like to work with you to see this update solves your challenges.

Please reach out if you have any questions.