Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange behavior of "Total Requests per Second" chart #889

Open
hoangphucITJP opened this Issue Sep 19, 2018 · 3 comments

Comments

Projects
None yet
4 participants
@hoangphucITJP
Copy link

hoangphucITJP commented Sep 19, 2018

Description of issue

Total Requests per Second's RPS drop to below 1 after the test start a while despite the RPS number on top keep rising

Expected behavior

The RPS of Total Requests per Second chart should keep updating according to the RPS number on top

Actual behavior

The RPS of Total Requests per Second chart value does not match the RPS number on top after the test start a while

Environment settings (for bug reports)

  • OS: Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-78-generic x86_64)
  • Python version: 2.7.12
  • Locust version: 0.9.0

Steps to reproduce (for bug reports)

I don't know what to put here but feel free to ask for any extra information. I can't provide the code though

Screenshot

imgpsh_fullsize

P/s: Sorry for ignored the template.

@klloveall

This comment has been minimized.

Copy link

klloveall commented Feb 7, 2019

I have also encountered this issue. I dug into the responses and it's happening because the /stats/request endpoint stops returning the "Total" stat block at the end of the stats list. This then causes the graph to show a RPS from a random path instead of from the total like it should. Interestingly, as is shown in the screenshot from @hoangphucITJP, the RPS in the header is still correct.

I tried to dig into the Python code and figure out what's causing it there, but haven't had much success there yet (mostly b/c I'm only running this in AWS, not locally so my debugging options are somewhat limited).

Please let me know if there's any suggestions as to how to solve this or any other debugging information I can provide.

@cgoldberg cgoldberg added the bug label Feb 7, 2019

@supermasita

This comment has been minimized.

Copy link

supermasita commented Mar 9, 2019

@cgoldberg I think my simple change should work as a fix (it has solved the issue for me). Thanks.

@supermasita

This comment has been minimized.

Copy link

supermasita commented Mar 11, 2019

@hoangphucITJP @klloveall - let me know if manually applying my change fixes your issue. I think my PR is correct, but it is not building for unrelated reasons. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.