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
Create stress/load test which should cover all APIs with mocked OP #360
Comments
Do we need to load test using tools like jmeter and mock OP using mockito? |
Yes to both.
|
duttarnab
added a commit
that referenced
this issue
Aug 12, 2019
duttarnab
added a commit
that referenced
this issue
Aug 12, 2019
duttarnab
added a commit
that referenced
this issue
Sep 4, 2019
duttarnab
added a commit
that referenced
this issue
Sep 4, 2019
duttarnab
added a commit
that referenced
this issue
Sep 7, 2019
duttarnab
added a commit
that referenced
this issue
Sep 8, 2019
duttarnab
added a commit
that referenced
this issue
Sep 9, 2019
duttarnab
added a commit
that referenced
this issue
Sep 9, 2019
duttarnab
added a commit
that referenced
this issue
Sep 9, 2019
duttarnab
added a commit
that referenced
this issue
Sep 11, 2019
duttarnab
added a commit
that referenced
this issue
Sep 11, 2019
duttarnab
added a commit
that referenced
this issue
Sep 11, 2019
duttarnab
added a commit
that referenced
this issue
Sep 13, 2019
duttarnab
added a commit
that referenced
this issue
Sep 13, 2019
duttarnab
added a commit
that referenced
this issue
Sep 13, 2019
Closed by #365 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create stress/load test which should cover all APIs with mocked OP.
Right now OP can process ~100req/s. Last time I've stressed oxd, it had similar performance which obviously was due to OP. It would be nice to mock OP and then stress tests against mocked OP. In this case we can see real numbers of oxd code (without limit that comes from OP).
The text was updated successfully, but these errors were encountered: