Closed
Bug 584800
Opened 16 years ago
Closed 15 years ago
Set up load test infra
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: telliott, Assigned: zandr)
Details
Two part bug:
Tracking the setup of the fully-hardwared sync stage cluster, where we'll be deploying load testing against.
Tracking the setup of the clients. My current understanding is that stage will be behind firewalls, making EC2 a challenge. mrz suggested using some available mac minis.
The number we'll need depends on how many 'users' we want to test for. A laptop client can generate approximately 20 transactions per second (minis may be higher). 1M active users (which is a bit under 50% of total users) requires 325 transactions a second. I believe that's higher than our spec (which, as I last recall, was 1M total users per db, suggesting we need somewhere on the order of 165 tps, or 9 machines)
Getting a single mini set up would let us test tps, as well as give us an image we can sync to the others.
| Assignee | ||
Comment 1•16 years ago
|
||
(In reply to comment #0)
> Two part bug:
Please don't do that unless you're filing bugs for each component and making them block this one. (Which is what you should do now)
Odds are any "two part bug" will have different groups working on each part.
[/me stops channeling reed now]
Comment 2•16 years ago
|
||
> Tracking the setup of the clients. My current understanding is that stage will
> be behind firewalls, making EC2 a challenge. mrz suggested using some available
> mac minis.
I said that before I understood what you were doing and specifically suggested doing some sort of job on the talos servers but that doesn't seem practical now.
Assignee: mrz → server-ops
Component: Server → Server Operations
Product: Weave → mozilla.org
QA Contact: server → mrz
Version: unspecified → other
Comment 3•16 years ago
|
||
This bug is really about standing up a load generation "cluster".
| Reporter | ||
Comment 4•16 years ago
|
||
(In reply to comment #1)
>
> Please don't do that unless you're filing bugs for each component and making
> them block this one. (Which is what you should do now)
Good point. Done.
Comment 5•16 years ago
|
||
whats the eta on this? this is blocking getting load tests going.
Updated•16 years ago
|
Summary: Load test client and server setup → Set up load test infra
Comment 6•16 years ago
|
||
I'll take this bug, as I'm sure I'll be setting up the hardware end of it.
I need to know what kind of hardware is needed and it needs to get ordered.
Is the "client" a desktop app? I noticed someone mention macbooks. Could we set up a cluster of old/used/intern MacBooks to do this? I'm sure we have a pool of used laptops somewhere, as interns are ending their internships?
Assignee: server-ops → jdow
Comment 7•15 years ago
|
||
After talking to zandr, it sounds like the "hardware" we'll be using for the client side load generation will be virtual machines running on the weave-kvm.mv.mozilla.com cluster.
Comment 8•15 years ago
|
||
I think my end of this is done. Punting to zandr in case there is anything left for this.
Assignee: jdow → zandr
| Assignee | ||
Comment 9•15 years ago
|
||
Man, there are a lot of bugs for this task. Done, running, Share and Enjoy.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
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
•