Difference between revisions of "Running many parallel instances"
Jump to navigation
Jump to search
old>Admin (Created page with "=== Preflight checklist === Before you go for a side-by-side setup please consider # Examine possibilities to use Exclusive group data ownership # Using docker containers ===...") |
old>Admin |
||
| Line 16: | Line 16: | ||
Move all .jar files from the war files /WEB-INF/lib folder, except for: p2eShared.jar. | Move all .jar files from the war files /WEB-INF/lib folder, except for: p2eShared.jar. | ||
The easy way to complete this this task is to rename the .war til .zip, move the files, and rename back to .war. | The easy way to complete this this task is to rename the .war til .zip, move the files, and rename back to .war. | ||
Revision as of 22:58, 3 July 2016
Preflight checklist
Before you go for a side-by-side setup please consider
- Examine possibilities to use Exclusive group data ownership
- Using docker containers
Adding more instances
Saving memory
Each application instance will consume 20 MB of PermGen memory (clasloader memory) if the document building functions are in use (approx. 5 mB instance if not). In order to reduce this amount to approx. 2 mB/application, all shared librarys could be moved to the webservers shared folder (Tomcat 6 is "lib").
This approach is only recommended if:
- You are running no other applications on that particular webserver (can be done)
- Sure that all applications will be using the same TS version
Move all .jar files from the war files /WEB-INF/lib folder, except for: p2eShared.jar.
The easy way to complete this this task is to rename the .war til .zip, move the files, and rename back to .war.