Wisdom from performance testing Ignition

Apologies for being evasive, I’m very experienced with (non-Ignition) full stack high throughput, high frequency development with less experience in a jvm environment. However, the question was how to measure performance, not to do a code review. I’m not above code review, that’s just not what I’m looking for.

  1. Is your decorator an implementation of this post?
  2. Yes, databases are optimized for data operations. I understand Named Queries > Expression > Script Transform, but how would I measure that? I can parse logs, but I’d ideally like a benchmarking toolkit for this type of discovery.
  3. I didn’t know you could enable caching with Named Queries, this looks like a better implementation than what I’m doing. Have you noticed any issues with stale data, where the client session doesn’t refresh automatically if a view isn’t reloaded?
  4. We use a separate database server within our cloud provider, where we don’t control network routing (presumably it’s over LAN, but I know some cloud providers virtualize that and only guarantee regional affinity). Given this architecture, my goal was minimize queries and offload processing to the client where possible.
1 Like