Versions Compared

Key

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

...

GET: 
Anchor
/threads/get
/threads/get

Will also be testing against different course sizes.

Expand
titleInvalid: Old test that was invalid due to the way mongo is set up

Using 10 locust users with min/max time of 1000/2000ms, GET requests for sent for either a single thread or randomly from a selection of 10% of the threads in a course. This was tested against a sandbox.

  • It seems like getting a random thread vs. the same thread does not make a reliably noticeable difference.
  • As number of posts in the database increase, the response time also increases.
  • Number of posts in a course does not seem to be matter for GETting a post. 

Update: This conclusion is invalid as the sandbox does not have the proper indexes. 

 

Approx Total PostsName# requests# failsMedianAverageMinMaxContent Size# reqs/sec
1000GET a random Thread out of 1000 Posts26710140150125.5698204410.569906211785.8
1000GET a single Thread out of 1000 Posts22620140151126.8491745337.106943111785.9
11000GET a random Thread out of 10000 Posts15220180196164.470911447.613000911786
11000GET a single Thread out of 10000 Posts15930180198164.4868851480.930805211785.8
11100GET a random Thread out of 100 Posts5420180193164.2448902419.183015811785.9
11100GET a single Thread out of 100 Posts7380180199165.0490761434.263944611786
12100GET a random Thread out of 1000 Posts6830180204166.1930084489.537954311785.6
12100GET a single Thread out of 1000 Posts10490180202169.2481041443.414926511786
13100GET a random Thread out of 1000 Posts14730180209171.40197751157.29904211786.1
13100GET a single Thread out of 1000 Posts13170180204170.7370281510.493993811785.8
14100GET a random Thread out of 1000 Posts8550190209175.9641171468.723058711786
14100GET a single Thread out of 1000 Posts75570190213173.6099721970.30401211785.1

...