Page MenuHomePhabricator

Audit CX frontend code for possible causes for save spikes
Closed, ResolvedPublic


I is unlikely that these spikes have been caused on purpose. We should audit our saving code for possible clues what could be causing this. We might get more information from T140619: Contact the user who was causing saving spikes to narrow down the search.

Event Timeline

Amire80 triaged this task as Medium priority.Jul 22 2016, 1:29 PM

Change 304804 had a related patch set uploaded (by Nikerabbit):
TranslationStorage: improvements to save throttling

Change 304804 merged by jenkins-bot:
TranslationStorage: improvements to save throttling

To check LogStash in few days to see whether this helped.

Logstash is dead quiet on this after last Thursday.