1580: mysqld hogging cpu on our reviewboard instance.

jtsh****@gmai***** (Google Code) (Is this you? Claim this profile.)
March 30, 2010 
What version are you running?
1.0.5.1


What's the URL of the page containing the problem?
dashboard and rest of the UI.

What steps will reproduce the problem?
Just keep the website up and running and you'd see mysqld always hogging 
cpu and there is a slow response navigating to dashboard and diffs

Swap:  8385880k total,       92k used,  8385788k free,  1113928k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
21531 mysql     15   0 1714m 259m 4924 S  205  6.8   4266:13 mysqld
29217 apache    18   0 65976  48m 5272 S   24  1.3   0:13.17 httpd
29393 apache    16   0 43624  26m 4424 S   13  0.7   0:01.45 httpd
29179 apache    15   0 51928  35m 5296 S    3  0.9   0:12.09 httpd


What is the expected output? What do you see instead?
I'm not sure as I need to find out if this is expected behavior or it's a 
poor configuration on our end.


What operating system are you using? What browser?
Linux 2.6.18 and IE and Mozilla browsers.
chipx86
#1 chipx86 
Review Board 1.0.6 will take some load off your server.

However, databases can be CPU, memory and I/O-intensive. Don't worry unless you're
noticing strange performance problems. If you are, move your database server off onto
a new system.

Also, I hope you're using memcached, as that will take the load off as well.
  • +NotABug
#2 jtsh****@gmai***** (Google Code) (Is this you? Claim this profile.) 
Yes, we've been getting tons of complaints from our development community that our
reviewboard instance is slow. Would you recommend some mysqld tweaks to improve some
of the performance besides upgrade to 1.0.6 release?
chipx86
#3 chipx86 
Didn't realize this was the VMware setup.

The dashboard is going to be slow until it's upgraded to 1.0.6. There are some major
issues with the dashboard in 1.0.5. They add stress to the database, and this will go
away once it's upgraded. I imagine it will help a *lot*.

I don't know what MySQL tweaks I'd recommend aside from moving it to a beefier
server. The best solution really is the upgrade.
#4 jtsh****@gmai***** (Google Code) (Is this you? Claim this profile.) 
Thanks for the quick response. Would upgrade to 1.0.6 version improve diffs display 
times, too?  That's another major painpoint for developers here. It takes a while to 
load up the diffs and folks are not happy about it.
chipx86
#5 chipx86 
For historical purposes, we've discussed this already outside of the bug report and
are looking into various solutions.