Ashwin,
There are no published benchmarks regarding OTM and it's ability to handle certain types of transactions. The application is too young and there user-base is to broad (using quite varied functionality) for this to be practical.
However, back and G-Log, I ran much of the application benchmarks and we used a variety of tests to test application performance between releases, patches and platforms:
- VolanoMark - Volano: The Volano Report & Benchmark Tests
- A great Java benchmark that is highly multithreaded (like OTM) and is very useful in determining relative Java performance between platforms and JDKs.
- Chat - Linux Benchmark Suite Homepage
- A great C-based benchmark that is highly multi-threaded. Great for determining native application performance on a platform, but not good at determining Java performance. For instance, AIX scores high on chat, since the CPUs and hardware are fantastic, but low on VolanoMark, due to the poor JDK.
- Custom integration (orders, saws, bulk plans, etc) via custom Perl and Python scripts. (Here are MavenWire, we're developing these again in Ruby -- our language of choice.)
- Custom Web UI actions (finders, searches, reports, etc) via custom JMeter scripts. JMeter is a free and highly-configurable web-scripting tool.
I can tell you that Solaris is the 3rd best platform for OTM, trailing Linux (1) and Windows (2) in terms of performance. In terms of stability, it's the 2nd best, trailing Linux. Just ensure that you don't use the Sun Niagara CPUs - they are intended for high-threaded, low computational applications and are provide VERY poor performance for OTM.
Thanks,
Chris