Open subotic opened 6 years ago
The thing is that it should protect GraphDB from malicious Gravsearch queries, but the limit should not be reached when doing reasonable things.
"Quadratur des Kreises"
What worries me is that the load-test actually does the same queries all the time. So why would then suddenly GraphDB hit the timeout? We should write a GraphDB load-test and see if we can provoke this. Maybe it is a bug in GraphDB?
We should write a GraphDB load-test and see if we can provoke this. Maybe it is a bug in GraphDB?
Good idea. Maybe GraphDB does some housekeeping periodically, during which queries are slower than usual?
@subotic Excellent idea!
Maybe we could dump the calls to GraphDB done during the load-test into files and then simply run those?
Maybe we could dump the calls to GraphDB done during the load-test into files and then simply run those?
Definitely. Then it would be easier to send the test case to Ontotext to ask them about it.
We are not the first ones to have this use case: https://github.com/buger/goreplay
Trying it out now to capture all requests to GraphDB. There are a lot of requests. After only a few minutes, the saved file is already around 150MB.
The query timeout is currently set at 5 seconds:
This will need some tweaking.