Сould you remove this restriction or increase the limits?
I’ve had this issue before when calculating dashboard statistics for a large amount of data. I ended up implementing pagination in my function, and iterating over the pages on the client to build up my dataset.
I’am calculate orders to show them on calendar. For this calculation i get indexes of orders with status and dates values, then calculate which orders meets the condition of dateFrom and dateTo. This not convenient to paginate
User want see on dashboard all orders not only part of it, will be nice if fauna remove this restriction, or make a special rate without limitation.
Fauna is a shared database service, so we impose reasonable limits on compute+resources to mitigate the “noisy neighbor” problem.
If you have reached the limit of resources for a single query, you should look at breaking your workflow into multiple queries.
Currently, there is no way to remove this restriction without impacting some other aspect of the Fauna’s operations, and there is no way to pay for such an alternative configuration.
Thanks, we are solved this problem.
But, where to get information about all restrictions. Few days ago we also face with function call stack limits. Will be nice to have page where, completely described all restrictions and also how to calculate metrics, optimizations features, etc.
Transactional limits are listed here: Limits :: Fauna Documentation
The stack limit is not listed there, in part, because it varies depending on memory use. It is ~200 levels of recursion.
Metrics are reported per query, as described here: Billing :: Fauna Documentation
You can find a few optimization strategies here: Best practices :: Fauna Documentation
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.