Description
When using priority messages with JDBC store, a query that recovers messages from the db can be very expensive due to the sorting it has to do. The best way I found to improve the performance of that query is to limit the sorting set by limiting the number of entries expected from the query. This assumes changing the actual query and is vendor specific.
Attachments
Issue Links
- relates to
-
AMQ-7368 Performance issue on PostgreSQL when we have lot of pending messages
- Resolved