95% of the work odata does is SQL queries to the vertica DB.
The config only allows 4 odata calls to run at once. The rest are queued and processed as the current 4 complete.
If that doesn't seem to be enough, that can be increased, depending on vertica specs and how long current queries take to run. And you'd want to make sure the additional queries in vertica don't effect other queries like reporting/thresholding/etc.
Original Message:
Sent: 04-09-2021 09:02 AM
From: Bruno Sousa
Subject: How to distribute the load for OData Query? Is it possible?
Hello
Is it possible to distribute the load from OData API Queries to the Data aggregator? (is it possible to use a backup DA for this, for example?)
Any strategies that you advise to optimize the load that API queries do to the system?
Thank you.
BR
Bruno Sousa