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)

x86_64
Linux
defect
Not set
normal

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.
Attached file link to github PR #209
Attachment #8490785 - Flags: review?(rhubscher)
Attachment #8490785 - Flags: feedback?(tarek)
Comment on attachment 8490785 [details] [review]
link to github PR #209

Let's try that.
Attachment #8490785 - Flags: review?(rhubscher) → review+
Whiteboard: [qa+]
Attachment #8490785 - Flags: feedback?(tarek) → feedback+
https://github.com/mozilla-services/loop-server/commit/6c03eeea204492f48cbf580fb61a00ba21904683
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
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: nobody → rpappalardo
QA Contact: rpappalardo
Flags: needinfo?(rpappalardo)
Will verify in 0.12.4 STAGE
Flags: needinfo?(rpappalardo)
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.

Attachment

General

Created:
Updated:
Size: