[bsteemson]

Results from the db server

stlsydhmlodb:mlop> time dd if=/dev/zero of=BigFile bs=1024k count=2048
2048+0 records in.
2048+0 records out.
real 0m14.47s
user 0m0.01s
sys 0m12.44s


Also have had the following feedback from Chirs Plough, so we'll be looking at increasing the weblogic threads and increasing memory on the webserver

The amount of memory on the web server is definitely to low. The benefit of JRockit is that it performs better than any other JDK, but does so by using a lot of memory outside of the Java Heap to optimize the code. So a 1GB Java heap can in turn cause the total Java process to use between 1.5 and1.75GB of memory. Apache will utilize another 125-256MB, which then doesn't leave enough for the OS and other processes.
The WebLogic Execute threads are still at the default of 50 and this is usually too low for any system that has a signifiicant number of web users and/or integration. This is easily adjustable by changing the config.xml.template file's ThreadCount parameter.
Having different platforms for the OTM Web and App tiers is a large potential issue. OTM makes RMI calls between these two tiers and if the JVM versions and codebase aren't identical - many issues can crop up, including performance, functionality and errors. The fact that the JVMs are from different providers (JRockit vs. IBM JDK) further complicates the issue.
I am also seeing high load on the DB server and agree that it attributes to poor web performance, but feel that the first two issues (memory and WL execute threads) may be a more immediate bottleneck.