Issue Details (XML | Word | Printable)

Key: BAM-1163
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: Richard van der Hoff
Votes: 0
Watchers: 1
Operations

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

Dashboard very slow

Created: 27/Apr/07 11:43 AM   Updated: 07/May/07 01:19 AM
Component/s: User Interface
Affects Version/s: 1.0.5
Fix Version/s: 1.1

Time Tracking:
Not Specified

Environment:
standalone version
Java HotSpot(TM) Server VM (build 1.5.0_11-b03, mixed mode)
Linux 2.4.26
Issue Links:
Reference
 

Participants: Ajay Sridhar [Atlassian], Edwin Wong [Atlassian], Mark Chaimungkalanont [Atlassian] and Richard van der Hoff
Since last comment: 1 year, 22 weeks ago
Number of comments: 8
Internal Work Bucket: Info Gathering
Labels:


 Description  « Hide
We are finding that the bamboo webapp is painfully slow to load any pages; for instance, the 'all plans' list typically takes about 45s to load. We have about 50 build plans, so this is almost a second per plan! Bamboo is running on a box with a hyperthreaded 3GHz processor and 2GB ram (which isn't doing much else) - so we really would hope to see better performance than this.

Is there anything we can do to help improve this?



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Ajay Sridhar [Atlassian] added a comment - 29/Apr/07 11:09 PM
Hi Richard,

Sorry for the inconvenience.

We are currently fine tuning the performance of Bamboo dashboard. This will be included in for the upcoming Bamboo 1.1 release (out very soon).

I was just wondering whether your Bamboo instance is hosted remotely or locally?

You could apply gzip compression to reduce the size of Bamboo's web pages. To do this go to the administration page -> Click on general configuration and tick the "Apply gzip compression to reduce the size of Bamboo's web pages?" checkbox and restart Bamboo for the configurations to take effect

Please let us know how your fared and we appreciate your patience while we get 1.1 out the door.

Cheers,
Ajay.


Richard van der Hoff added a comment - 30/Apr/07 06:17 AM
Thanks Ajay, but our Bamboo is hosted locally. I'm pretty sure the delay is on the server side.

In fact, I tried running a jstat against the jvm running Bamboo, and noticed a couple of odd things. Fisrtly, the permanent generation usage rapidly builds up to 99% (increasing the -XX:MaxPermSize argument increases the time taken to get to 99% but doesn't stop it), and it seems to be doing a young generation garbage collection at least once a second, even when nothing is in the build queue. The first strikes me as particularly strange - is it normal?


Ajay Sridhar [Atlassian] added a comment - 01/May/07 01:24 AM
Hi Richard,

Thank you for that information.

I was just curious whether you measured the permanent generation usage while Bamboo was building? Or does this happen all the time?

Hopefully, the performance upgrade in 1.1 will address these issues.

Cheers,
Ajay


Richard van der Hoff added a comment - 01/May/07 07:29 AM
I've now realised that the permanent generation expands as necessary, so the fact it sits at 99% is probably not as relevant as I first thought. It does still gradually creep up even when no builds are happening - I guess this is just accesses to the UI, however.

I look forward to anything that can be done to speed things up. To be honest, I'd prefer it if there was a way of using it without any ajax at all...


Ajay Sridhar [Atlassian] added a comment - 01/May/07 11:19 PM
Hi Richard,

Sadly, there is no way to use Bamboo without the AJAX stuff (However, this is a really good idea).

Again, most of your problems should be resolved with the Bamboo 1.1 release.

Cheers,
Ajay


Mark Chaimungkalanont [Atlassian] added a comment - 03/May/07 06:42 AM
Richard,

You should be able to improve the performance of the dashboard if you do some tweaking of your applicationContextUser.xml (in your WEB-INF/classes directory).

If you modify the lines:

<bean id="bambooUserManager" parent="txWriteProxy">
    <property name="target">
...
  </bean>

and change it to use a "txReadWriteProxy" instead like

<bean id="bambooUserManager" parent="txReadWriteProxy">
    <property name="target">
...
  </bean>

Please let us know if this makes any difference or not.

Cheers,

Mark C


Richard van der Hoff added a comment - 03/May/07 07:53 AM
Hi Mark, thanks for that. It does seem to have improved matters significantly - we're now down to a few seconds to load the 'All plans' list!

I think there's still room for work on the round-trip time for some of the ajax updates, but this is a vast improvement, so thank you!


Edwin Wong [Atlassian] added a comment - 07/May/07 01:19 AM
Richard,

Glad to hear that's helped out.

We'll mark this issue as resolved for now. Please let us know if you do run into any other issues.

Regards,
Edwin