Record addition or update appears after 30 minutes!! Why is this delay caused?
Use this gist to connect directly to your database and check if the data is being update in realtime
If you want You can run this to clear the cache
docker exec -it appwrite-redis redis-cli
# then
127.0.0.1:6379> flushall
To see if it then updated on the spot in the console
Just know that flushing the cache can interfere for queue jobs so use it only if all of your code works in async most of the time
If this solves the problem. How can I fix this permanently?
Will manual cleaning always be required this way? How can I update redis settings? do you have a suggestion?
It fixed it?
I'll try it in an hour when it slows down completely.
From what I see it should clear the cache But, first let's make sure this is the problem before digging into it
flushall
I ran it and it's back to normal
my problem seems to be redis cache.
This is how I added events to a function. for how it should work
I am adding a record to these collections. but the event starts Function Executions after 30-40 minutes.
collections.647f40efa6de6e094841
event triggers are running too late.
@Binyamin Where do you think I can fix this?
I think maybe it because you have too many events in a given minute Do you get error on running functions?
bigint(20) unsigned changed to double
now no error π
no errors at the moment it works flawlessly.
unable to write stats data.
So you have error right now?
I think maybe it because you have too many events in a given minute
This is the problem but 50 devices are working right now.
If 1000 devices send data to the server, if the event runs, appwrite will fire.
won't the appwrite system be able to manage this?
Will be able but those events are in a queue one after each other using <:redis:1042565927952199811> Redis. For most use-case the 6GB ram sound pretty enough for me.
If you continue to experience this delays with the databases I'll recommend decentralizing the databases.
