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

The "time" result should be taken from across multiple requests and not a single request #37

Open
motin opened this issue Dec 10, 2015 · 2 comments

Comments

@motin
Copy link

motin commented Dec 10, 2015

Currently, the "time" results is taken from a single request

I suggest we use the result that ab already reports "Time per request: 78.445 ms" which is the mean based on all requests. It would also be interesting to use ab's "Time per request: 7.845 [ms](mean, across all concurrent requests)" for comparison reasons.

@kenjis
Copy link
Owner

kenjis commented Dec 10, 2015

Yeah, I also want to fix the problem. Once is too less, and the value is not stable.
But ab's time is not the same.

@motin
Copy link
Author

motin commented Dec 10, 2015

What about taking ab's time for each framework and then subtracting ab's time for "no-framework" requests? That would give the actual real-world additional bootstrap cost for the framework. Related discussion: #34

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants