It's all about the answers!

Ask a question

Build Forge performance on WAS / New Java engine


Jozef Vandenmooter (16332933) | asked Jan 07 '15, 3:57 p.m.
edited Jan 07 '15, 3:57 p.m.
Hi all,

Does anyone have experience with GUI performance improvements resulting from switching Build Forge from Tomcat to WebSphere?

How about performance improvements resulting from switching to the new Java engine (MJC)?

Thanks,

Jozef




Accepted answer


permanent link
Kyungmo Jung (41) | answered Mar 18 '15, 9:45 p.m.
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
Jozef Vandenmooter selected this answer as the correct answer

Comments
Jozef Vandenmooter commented Apr 08 '15, 1:52 p.m.

Thanks a lot for the info Kyungmo!

Jozef

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.