Performance Tips

Performance Tips

HZN Queue Console fetches messages on demand and renders them in the UI. With very large queues or slow networks, a few settings can make a significant difference.

Reduce the Fetch Limit

By default the app fetches a limited number of messages per queue. If a queue has hundreds of thousands of messages, fetching all of them at once will be slow and memory-intensive.

  • Use the rows-per-page control in the message table to fetch fewer messages at a time.
  • Apply filters before fetching — this reduces the number of messages transferred from the broker.

Use Filters Before Browsing

Loading a queue with a million messages and then filtering client-side is expensive. Instead:

  1. Open the queue.
  2. Set your filters before clicking refresh.
  3. The broker evaluates the filter server-side and returns only matching messages.

This is especially effective for filtering by header values or routing key.

Limit the Number of Open Queues

The app refreshes queue stats for all visible queues on a polling interval. If you have many servers and queues expanded at once, background polling adds up.

  • Collapse queue sections you are not actively using.
  • Disconnect from servers you are not working with during a session.

Slow Connection to a Remote Broker

If the broker is on a remote server:

  • Check network latency: ping <broker-host> from your terminal.
  • High latency multiplies across many API calls. Consider using a VPN with a closer exit node, or running the app on the same network as the broker.
  • For Custom licenses, consider deploying the app as a web service co-located with the broker to eliminate network round-trips for the browser.

Large Message Payloads

Messages with very large payloads (>1 MB) slow down rendering in the detail panel.

  • Use Table View to scan messages by specific fields without loading the full payload.
  • Export a subset of messages to a file and analyse them offline if the payloads are too large to inspect in the UI.

App Feels Slow After a Long Session

The app can accumulate memory after browsing many large queues in a single session. Restarting the app resets memory usage without losing your configuration.