[Buildbot-commits] [SPAM] Re: [Buildbot] #829: Buildbot 0.8.0rc2 master uses huge CPU while builds are running

[Buildbot]

#829: Buildbot 0.8.0rc2 master uses huge CPU while builds are running
---------------------+------------------------------------------------------
Reporter:  bdbaddog  |       Owner:       
    Type:  defect    |      Status:  new  
Priority:  critical  |   Milestone:  0.8.0
 Version:  0.8.0     |    Keywords:       
---------------------+------------------------------------------------------

Comment(by bdbaddog):

 O.k. I think I found at least one of the issues, I added a bunch of debug
 output.

 Here's a "smoking gun" I think.
 2010-05-16 15:51:56-0700 [HTTPChannel,0,192.168.17.248] Before
 running:SELECT filename FROM change_files WHERE changeid=?
 2010-05-16 15:51:58-0700 [HTTPChannel,0,192.168.17.248] After
 running:SELECT filename FROM change_files WHERE changeid=?

 There's no index on changeid in table change_files. So it's doing a table
 scan per select. (thus 2 seconds per query)
 I'm adding an index for that table:
 create index changeid on change_files (changeid);

 And voila.. The response time for the waterfall is back to normal.

 What's the best way to change this in the current code.
 I see db/schema/tables.sql and db/schema/v{1,2,3,4}.py

-- 
Ticket URL: <http://buildbot.net/trac/ticket/829#comment:31>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation