We have encountered a strange problem.
If we apply our application and then restart the weblogic portal server; And when we do a load test, the load test fails with very high reaction time and low throughput. If we check the load for the second time, then it just runs fine.
If we apply only our application, but do not restart the weblogic portal server then loadtest runs fine.
Any hint is very useful
This hotspot looks like JVM warming - when you restart the server , Then there are only more codes to compile. Whenever you are benchmarking or loading Java application, it is a good idea to first get a soft hammer to get all the code that is compiled, this is especially true of server applications that have been running for a long time Must have been
Update: I thought I should make it clear that the curriculum has already been compiled for the bytecok and I compiled the additional compilation of the native code of JVM.
Comments
Post a Comment