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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems after doing some simple load testing that we're taking ~140ms to return results from the .get() method on the first request. Subsequent requests are obviously lightning fast because the data is stored in memory.
This isn't a huge deal for clients that only make a few requests, but if you have to request hundreds of different paths, then this is a huge performance bottleneck.
For now I'm treating this like a bug, because it feels wrong that it should take this long. Will dig into it and put my results here when I'm done.
The text was updated successfully, but these errors were encountered:
It seems after doing some simple load testing that we're taking ~140ms to return results from the
.get()
method on the first request. Subsequent requests are obviously lightning fast because the data is stored in memory.This isn't a huge deal for clients that only make a few requests, but if you have to request hundreds of different paths, then this is a huge performance bottleneck.
For now I'm treating this like a bug, because it feels wrong that it should take this long. Will dig into it and put my results here when I'm done.
The text was updated successfully, but these errors were encountered: