Paul Mander wrote:
>
> WAS test: 32,577ms
> Tomcat test: 439ms
>
> Going to turn off the filter for the trinidad classes and see where the
> WAS CPU is giong.
>
>
Correction: After looing into the reasons why websphere was taking all the
CPU, I found that my WAS profile was configured to output trace level
details to a log file for all jsf packages (a previous do to with encoding
characters on a PPR request). The corrected results are as follows:
WAS test: 26315ms
Tomcat test: 439ms
Now, enabling tracing of any classes in the packages org.apache.myfaces.*
shows a baseline for tomcat executing (chagned its JDK to WAS JDK to try and
keep as many things the same as possible) of 22885ms.
This is much higher than the 439ms as profiling all these classes takes
time. Running the test with the exact same profiling but ni WAS gives 46668
(more than double).
now for the org.apache.myfaces.* packages
WAS: 22869
Tomcat: 22092
Which for arguments sake are identica. But, we have 24576 unaccounted for in
WAS as an overhead that is currently being filtered.
--
View this message in context:
http://old.nabble.com/-Trinidad--Trinidad-consuming-80-90--CPU-tp27068136p28752758.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
