Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Image Removed

    After adding the index for "last_activity_at", we did not see a noticeable improvement in response time and the 95th percentile was still unusually high. There was a significant improvement in the error rate. The chart below shows a visual correlation between spikes and the response time. Upon inspecting these remaining errors, it was found that they all shared the "asc" sort field in common. This could explain the unexpected response time where we were expecting an improvement. 

 

Image Added

 

Expand
titleData from the live index

The test started at 3:50pm. The index started at 4:00pm. The index finished at 4:28pm.

Image Added

Coursereqs#failsAvgMinMaxMedianreq/s95%
LargeGET_comment_list600(0.00%)38619110953300760
 GET_thread35410(0.00%)240919412201.8360
 GET_thread_list1620238(12.81%)103718753809200.72200
 PATCH_comment600(0.00%)51922611314800970
 PATCH_thread650(0.00%)38417320593200770
SmallGET_comment_list18460(0.00%)24015211712100.4400
 GET_thread1110040(0.00%)222-25239520026.1340
 GET_thread_list59369151(0.25%)603-25581755012.81200
 PATCH_comment18377(0.38%)40218225823500.4770
 PATCH_thread199535(1.72%)31014816112700.4550

 

After removing the "asc" parameter, we saw some improvement but unfortunately, because of the way PATCH was implemented in the loadtest, it caused the response times to gradually become slower. At this point in time, because "asc" was not being used by the browser and will not be used by the mobile app, adding that index has been bumped down in priority.