GUI API calls not waiting for a response

[lukerosser]

Version: 7950d4a (latest commit of 0.73.3)

If/when the server is under load the GUI continues to send refresh API calls even without a response

Would it be better to not send another API call until the previous one has a response? To not add load to the server and allow for the timeout settings to work as it may complete the first call, just slower than the current refresh rate

[scudette]

Generally we cant wait for responses - we generally just cancel the old call and issue new ones. Otherwise the GUI can get stuck without being able to update.

I think in this case the call is not cancelled properly which is probably a bug - we should add it. However, generally this call should not even be doing any IO because user traits are cached on the server so im not sure why it is taking so long.

Are you able to collect profiles to understand why the server is slowing down?
https://docs.velociraptor.app/docs/deployment/troubleshooting/#debugging-the-server