All read requests such as config and query read would update the database about the node info. However, these updates would become a bottleneck for database performance.
I understand that many functions reply on the last seen timestamps, but it would be not scaleable with such heavily written requests to the database. I have two ideas, one is to store these data in Redis/memory and update them periodically. Another is that we process these changes async.
In our test, we only have 3 req/s but the latency between database and osctrl is around 50ms.
Looking forward to hearing from your idea.
All read requests such as
configandquery readwould update the database about the node info. However, these updates would become a bottleneck for database performance.I understand that many functions reply on the last seen timestamps, but it would be not scaleable with such heavily written requests to the database. I have two ideas, one is to store these data in Redis/memory and update them periodically. Another is that we process these changes async.
In our test, we only have 3 req/s but the latency between database and osctrl is around 50ms.
Looking forward to hearing from your idea.