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
We want to add a stress test (or two!) to the API proxy designed specifically to provoke a worst-case alert geometry scenario for the API interop layer. In a real world example we observed recently, we had an alert spanning 16 forecast zones, with each zone having its own complex geographic shape. The geographic query and resulting point collection (over 10M of responses from the database) exhausted all memory on the API interop layer.
This stress test can then be used to measure improvements to the API interop layer -- how fast do we respond with that query? How much memory do we take up? Are our optimizations for this kind of query working?
Description
We want to add a stress test (or two!) to the API proxy designed specifically to provoke a worst-case alert geometry scenario for the API interop layer. In a real world example we observed recently, we had an alert spanning 16 forecast zones, with each zone having its own complex geographic shape. The geographic query and resulting point collection (over 10M of responses from the database) exhausted all memory on the API interop layer.
This stress test can then be used to measure improvements to the API interop layer -- how fast do we respond with that query? How much memory do we take up? Are our optimizations for this kind of query working?
CC @eric-gade
Acceptance criteria
The text was updated successfully, but these errors were encountered: