DB JMS performance

[pixel]

We have an application with a queue, through which we are putting thousands of small, very quick, requests. With a non-persistent queue, performance is very good. However, the moment we change to a persistent queue we are seeing huge IO bottlenecks on the JMS tables. This is on Oracle 10g.

Are there any ways to optimize the performance of this. One possible solution we thought of was to use in-memory tables on Oracle, but we may not be using Oracle long-term anyway.

Any help is much appreciated, we need the security if persistent queues, but the IO overheads are killing us.

[genman]

That's JMS for you, it mostly comes down to I/O bottlenecks.

You might get better results from MySQL, especially if it is located on the same machine. Oracle is traditionally hard to tune (IMHO) unless you have a Oracle expert.

[pixel]

thanks genman, I'm currently in the process of switching to OCI instead of the thin driver; some fairly derogatory comments towards the lineage of the thin driver suggested the switch might help.

After that I'll try MySQL - the price is certainly better