Crash submission very slow

RESOLVED INCOMPLETE

Status

Socorro
General
--
blocker
RESOLVED INCOMPLETE
7 years ago
6 years ago

People

(Reporter: laura, Assigned: lars)

Tracking

({regression})

x86
Mac OS X
regression

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

7 years ago
Several reports that this is slow, and this is reproducible.

We need to work out where the bottleneck is, but this is hard.

Some possible solutions:
- add more collectors
- add more processors (on hadoop nodes???)
- check mod_wsgi configuration
- network perf between collector/processor
(Reporter)

Updated

7 years ago
Assignee: nobody → lars
Keywords: regression
(Assignee)

Comment 1

7 years ago
patch to collector to resolve the exception that aravind noted this morning is in r2506
I saw a slow submit this morning, FWIW. I watched the crashreporter client sit and spin for >30s while submitting. (I was waiting for it to quit so I could reboot Windows to apply updates.) The report says it finished submitting at 8:59 AM EDT.
(Assignee)

Comment 3

7 years ago
Created attachment 475559 [details]
at patch to correct an error in throttling

The crashStorage employed by the collector included an error that would result in an exception being thrown for crashes that are not passing throttling.  This corrects that problem.
(Assignee)

Comment 4

7 years ago
Created attachment 475671 [details] [diff] [review]
the addition of the procsubmitter

this is the addition of the procSubmitter cron job and the rollback of collector/processor communication
Attachment #475671 - Attachment is patch: true
Attachment #475671 - Attachment mime type: application/octet-stream → text/plain
Attachment #475671 - Flags: review+
(Reporter)

Updated

7 years ago
Attachment #475671 - Flags: review+
(Assignee)

Comment 5

7 years ago
we'll address the issue again at a later date
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.