This popped up in my Twitter feed earlier: -
Let me explain what multi-tenant JVM really is. In a traditional model every time you type "java xyz" you start new operating system process and run single application per OS process with entire JVM dedicated to serving your app. If you have very large application (say WebSphere Application Server Network Deployment) with many different different WAR and EAR files deployed into that server having one JVM per "application" is not a bad idea. In this case WAS ND provides "operating environment" for multiple applications that you deployed into it and it makes a good use of the JVM and OS resources and under high load with proper tuning and proper applications can consume up to 100% of CPU and memory available to the OS. This is how JVMs from OpenJDK, Sun JDK and IBM JDK used to work in the past (and still do).
…
No comments:
Post a Comment