Build Forge performance on WAS / New Java engine
Accepted answer
Hello Jzef,
1. About UI performance
From my experience, GUI performance is same in WebSphere and Tomcat.
The most significant factor to UI performance database usecase.
Purging job is most high performance cost work in Build Forge. Purging will more impact on performance if step logs contain more lines because purging job mostly deletes database records(build jobs, environments, logs).
I would like to advise below to improve UI performance.
Create purge classes and schedule the classes to run system idle time for Build Forge purge not to run purge jobs during working time during developers use UI.
Build Forge don't run purging if purge classes are scheduled.
2. MJC performance
MJC performance is significantly improved compare to Perl engine. MJC changed design agent connection mechanism and allocate server to job.
MJC will give much higher performance if long(many) steps are supposed to run in a project.
Thanks,
Kyungmo Jung
1. About UI performance
From my experience, GUI performance is same in WebSphere and Tomcat.
The most significant factor to UI performance database usecase.
Purging job is most high performance cost work in Build Forge. Purging will more impact on performance if step logs contain more lines because purging job mostly deletes database records(build jobs, environments, logs).
I would like to advise below to improve UI performance.
Create purge classes and schedule the classes to run system idle time for Build Forge purge not to run purge jobs during working time during developers use UI.
Build Forge don't run purging if purge classes are scheduled.
2. MJC performance
MJC performance is significantly improved compare to Perl engine. MJC changed design agent connection mechanism and allocate server to job.
MJC will give much higher performance if long(many) steps are supposed to run in a project.
Thanks,
Kyungmo Jung