Closed
Bug 647321
Opened 14 years ago
Closed 14 years ago
Upgrade sm-selenium01
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: clouserw, Assigned: phong)
Details
I'm trying to use sm-selenium01 today and it's unbearably slow. Like, click something wait 30 seconds kind of slow. If I recall, this is on a shared VM - can we make sure that box isn't overloaded?
It claims to be a 3ghz CPU (doesn't feel like it?), and a gig of RAM which seems alright. I get the feeling the disk i/o is the problem, but don't have a way to prove that.
How hard is it to make this faster?
Comment 1•14 years ago
|
||
phong, I don't see this in inventory. Is it a VM that could be moved to faster storage?
Assignee: server-ops → phong
Reporter | ||
Comment 2•14 years ago
|
||
I'm pretty sure it's disk I/O. I tried installing vim and after 35 minutes of it churning I left and came back a couple hours later and it was done. On the other hand, if I just leave it alone, it runs Firefox well enough to run the tests we need.
So, short story is this isn't a high priority, but I'd like to get it on the radar so we can expand our testing coverage.
Assignee | ||
Comment 3•14 years ago
|
||
This is a VM. I can try to move it to better storage. It also doesn't have vmwaretools installed. This would help the performance. When can I take this down to move it?
Reporter | ||
Comment 4•14 years ago
|
||
How long will the downtime take?
Assignee | ||
Comment 5•14 years ago
|
||
It's only 12GB. Probably about 30 minutes at most.
Reporter | ||
Comment 6•14 years ago
|
||
Oh, sweet. As long as we have notice, any time.
Assignee | ||
Comment 7•14 years ago
|
||
how about now? or do you want to wait for next tuesday during a downtime window?
Reporter | ||
Comment 8•14 years ago
|
||
to be clear, notice doesn't need to be long, just tell us so when our tests start failing we know why.
Assignee | ||
Comment 9•14 years ago
|
||
all done.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•