Closed
Bug 1006698
Opened 10 years ago
Closed 10 years ago
Create a Loop Server Stage environment for load testing
Categories
(Hello (Loop) :: Server, defect)
Hello (Loop)
Server
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jbonacci, Unassigned)
References
Details
(Whiteboard: [qa+])
Because it's no fun running load tests on my localhost. Stage environment will be used for remote/functional testing, load testing, sizing/scaling for Production, similar to other Services projects. /cc Dev /cc OPs
Reporter | ||
Updated•10 years ago
|
Whiteboard: [qa+]
Comment 2•10 years ago
|
||
(In reply to Tarek Ziadé (:tarek) from comment #1) > What do we need to do to move this forward ? :benson is putting the finishing touches on the Puppet module now. I believe we will be able to deploy a stack soon.
Flags: needinfo?(bobm)
Comment 3•10 years ago
|
||
Done. https://loop.stage.mozaws.net I spun it up w/ 3x m3.medium since these are single processor machines. It is backed by a single m1.small redis instance. Nothing special. The code that is running is loop-server@dc9b8d2ce728a011bf9aa02ed2ded41f4bb98e7c. I pushed a bug fix into the loop-server repo a little while ago. Not sure if loop is CPU intensive (does crypto/number crunching). If it does we should look into how to better use multi-core machines better.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•10 years ago
|
||
Verified the AWS setup in US East. Will leave this ticket open until I can get some test to work against Stage (remote/load)...
Comment 5•10 years ago
|
||
It shouldn't be CPU intensive: the only operation it does is cyphering/signing with aes-128-cbc and sha256 hashes (which shouldn't be CPU intensive). Anyway, load testing will tell us that.
You need to log in
before you can comment on or make changes to this bug.
Description
•