Ideal value for limit

I am using a job that queries the BitQueryAPI daily for getting price data. I have also made a paginated function that is supposed to query the full price history of a coin.

What is the supported maximum number of rows that can be returned in one API call defined by the limit parameter?

The limit parameter basically limits your result to the amount “to be limited” passed along with it. If the limit has been set to 10, the API limits the returned data to 10 rows. The maximum number of rows returned in one API call defined by the limit parameter can be the total number of JSON formatted queries processed by the API i.e. basically the complete available data.

@sayon When I try to execute queries using an API key with limit > 10000, I went up getting errors, usually Error 500: Bad Gateway which go away when I reduce the limit. So my question is, what is the hard limit to how many rows can be queried from the API in one call for price data? Does this limit change for the paid API

There is no hard limit on how many rows can be queried, however, if you increase the limit, you will increase the server memory used while querying the data, which has limitations in the backend.

So there is no limit on how many rows can be queried (As of now), rather than there is a limit on how much memory will be used while querying the data in the backend.

@gaurav so this also depends on the traffic on your backend I assume?

  1. What is the limit on the memory that can be used? For example I would like to query the entire price history of the BNB coin, how many smaller requests should I break this into?
  2. Can you give some insight into when (what time during the day) do you have the least load on your servers?
  3. Are these memory constraints removed while using the paid API?

The memory constraints aren’t removed with the paid version. You have to optimize your query by setting limits and other filters.