History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CIB-943
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Trivial Trivial
Assignee: jason
Reporter: Eric Scheie
Votes: 2
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pulse

Slow UI performance with 39 projects.

Created: 19/Feb/07 08:02 PM   Updated: 26/Feb/07 06:44 PM
Component/s: Web UI
Affects Version/s: 1.2.16
Fix Version/s: 1.2.18

Environment:
SuSe Enterprise Linux Server 10
2 Intel 3.8 Ghz CPU w/ Hyperthreading
6 GB RAM


 Description  « Hide
It seems like with the addition of every new project the pulse response times get slower and slower. Our plan was to disable the master agent and just use that server to drive the UI. I setup a test pulse master using our existing pulse database and disabled the agent. Even though I was the only one accessing the server on some decent hardware and with no builds being performed, I still experienced 20 second plus response times clicking between the project page and project dashboard screens.

Pulse is an awesome product, and I know a lot of data is being displayed on those screens, but it would be great if the UI was a little more performant. We use the project dashboard page as the main status page for all the projects. From there you can drill down into FishEye, JIRA, and our Wiki.

Question - Will using an external database like MySQL increase the UI performance?

BTW, I love the display of the projects tab. I wish user dashboard pages had the same look and feel!

Thanks,
-Eric

 All   Comments   Change History      Sort Order:
Todd Papaioannou - 19/Feb/07 11:33 PM
Why not give the user the option to make the projects dashboard their default page?

Daniel Ostermeier - 20/Feb/07 02:58 AM
Hi Eric,

I expect that part of the performance problem is that the embedded HSQLDB uses the same resources that are used by the pulse UI. So yes, I would expect that moving to an external database like MySQL would improve the UI performance.

Can I ask roughly how many builds you have with those projects, so that we can get some idea of the size of your pulse data set and have a starting point for investigating performance improvements.

As for allowing the projects dashboard to be a users default page, we can certainly to do that. I have created a new issue: CIB-944 to track this.

Cheers,
-Daniel

Eric Scheie - 20/Feb/07 07:49 AM
Hi Daniel,

Thanks for creating and resolving CIB-944 already. Looking forward to that!

The max number of builds for any given project we have in pulse is 2505 but the average is closer to 100 builds per project. The pulse data directory is roughly 50GB in size. Is this configuration extraordinary in anyway? Have you noticed slow response times with similar configurations?

I am planning on configuring pulse to use MySQL tomorrow so I will let you know if I notice any performance improvements. I can provide you with a copy of our database if it helps you out at all.

Thanks again,
-Eric

jason - 25/Feb/07 04:20 PM
Several performance improvements have been rolled into Pulse 1.2.18. These should dramatically improve load times for the main Pulse pages.

Eric Scheie - 26/Feb/07 06:44 PM
I just installed Pulse 1.2.18 and am very impressed with its performance.

Thanks!
-Eric