I just noticed that I hit the 500k db reads limit on my very small next js app with the most data being present in one collection having around 50 documents.
I do use a lot of relations to link the collections. When creating a relation to another collection, I usually do a 2 way relationship. Is this the root cause?
Or could it be something like infinite loops on the app, calling the database?
Any suggestions on how to diagnose and fix?
How many related docs do you have?
Fyi, relationships are experimental and should be used with caution as they may lead to performance issues
Relationships could be related. Every related document adds to the DB read count
For example I have a collection that is realted to 4 other collections, one of which is a one to one relationship and the remaining three are many to one or many to many
So if I read 10 documents in a collection which has 4 relations to other collections, then the total reads will be 10 + (10 x 4) total of 50 reads on the DB? What if those related documents contain relations to other collections? Will the read count cascade multiply for each document read?
Yes, every document returned is 1 read
Recommended threads
- Google/Apple OAuth to show continue to "...
hi everyone, I am building a react-native app with expo and appwrite. I have setup an OAuth flow with Google and Apple following this doc (https://appwrite.io/b...
- Function permissions
In my app I have a CreateUser flow which makes several documents and at the end uses the functions.createExecution() to call a server-side function to create a ...
- Google Auth not working in a React App
Authentication with Google has failed. It redirects back to the signin route in React. Attached screenshots for configuration of Google console and Appwrite Go...