TestEngineering/Services/LoopServerLoadTesting: Difference between revisions

TestEngineering/Services/LoopServerLoadTesting (view source)

249 bytes added , 19 September 2014

Confirmed users

3,727

edits

@@ Line 371: / Line 371: @@
   nginx logs:
-  Some percentage of 200s, 204s, and 404s is acceptable. Some of the 404s are actually bot/spam
+  The 200s (good stuff) and 101s (websockets) are acceptable.
-  activity in the /media/ephemeral0/nginx/logs/loop_server.access.log and
+ The 499s are an artifact of the current load testing tool (V1).
-  /media/ephemeral0/circus/loop_server/loop_server.out.log logs.
+  You should only see them at the end of the load test.
+ Right now, we are getting a lot of 404s and 307s.
+  They all appear to be caused by bots. There is a bug open about this.
   Any percentage of 405s, 502s, or 503s is not acceptable.
+ Application logs:
+ Right now, we are getting a lot of 404s and 307s.
+ They all appear to be caused by bots. There is a bug open about this.
+ See the loop_server.out.log file.
   /var/log/loop_err.log