Closed
Bug 527486
Opened 16 years ago
Closed 16 years ago
Move TestSwarm to New Server
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jeresig, Assigned: jeresig)
References
()
Details
(Whiteboard: [waiting on db contents])
TestSwarm has outgrown it's old VM and needs a new home. It's growing rather rapidly - and that's without many projects hooking in to it (right now only jQuery and jQuery UI are hooked in).
So far only 250 jobs have been submitted and about 10 gigs of data is being stored. That works out to about 41MB per job submitted (I expect this to be in the dozens of jobs per day when it's fully operational). Thankfully, the majority of that data is just HTML file dumps and could probably be stashed/compressed somewhere.
The server load is quite high right now (both in CPU and memory usage) so anything to alleviate that strain will help, as well.
I'll be doing some more rewriting on my end, to try and fix things up, so we'll hopefully find a good middle ground to work from.
Comment 1•16 years ago
|
||
zandr, can you provide an eta? looks like you have a machine allocated but not built?
Comment 2•16 years ago
|
||
PXE was disabled on both onboard NICs. Enabled, building.
Comment 3•16 years ago
|
||
Up @ 10.2.11.230, updated HP tools & firmware.
Comment 4•16 years ago
|
||
Up at lm-testswarm01.labs, testswarm installed from git, account created for jeresig.
John, comment here when you want me to move DNS to point at the new host.
Updated•16 years ago
|
Whiteboard: [waiting for content]
Updated•16 years ago
|
Whiteboard: [waiting for content] → [waiting on db contents]
Comment 5•16 years ago
|
||
Never heard anything more about this. Let me know when you want DNS moved.
Assignee: zandr → jresig
Comment 6•16 years ago
|
||
Nothing heard, closing.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Updated•11 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
•