Closed
Bug 1068667
Opened 10 years ago
Closed 10 years ago
Investigate why the CPU is so high during the load tests.
Categories
(Hello (Loop) :: Server, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: alexis+bugs, Assigned: rpapa)
Details
(Whiteboard: [qa+])
Attachments
(1 file)
James found in bug 1067397 that the CPU usage and the memory were high even once the load tests were over.
We should find out what the problem is and fix it.
One potential problem is that we're not currently clearing the setTimeout we created. Let's try to go this way and see if that fixes our problem.
|
Reporter | |
Comment 1•10 years ago
|
||
Attachment #8490785 -
Flags: review?(rhubscher)
Attachment #8490785 -
Flags: feedback?(tarek)
|
||
Comment 2•10 years ago
|
||
Comment on attachment 8490785 [details] [review]
link to github PR #209
Let's try that.
Attachment #8490785 -
Flags: review?(rhubscher) → review+
|
||
Updated•10 years ago
|
Whiteboard: [qa+]
|
||
Updated•10 years ago
|
Attachment #8490785 -
Flags: feedback?(tarek) → feedback+
|
|
||
Comment 3•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
Assignee | |
Comment 4•10 years ago
|
||
I see this went into 12.2 and don't recall any issue when testing with :jbonacci, but I can reverify on next loadtest cycle.
|
|
Assignee | |
Updated•10 years ago
|
Assignee: nobody → rpappalardo
|
|
Assignee | |
Updated•10 years ago
|
QA Contact: rpappalardo
|
|
Assignee | |
Updated•10 years ago
|
Flags: needinfo?(rpappalardo)
|
|
||
Comment 6•10 years ago
|
||
So, on a single, c3.large instance, a "normal" load test takes and holds 75% CPU.
It does get released when the test is over, which is good.
I am not sure there is much more we can do here, short of rewrites, so calling this one fixed.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•