-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve the gpu indexing with the change in number of nodes #322
Comments
we kept the periodically running ticker to requery the nodes and upsert the GPUs info each hour. but this focus on enhancing the indexing process for newly added nodes, not for the nodes updated with add/remove gpu, also considered using a trigger depending on another field that changes whenever a new GPU is added, even if it's added to a node already in the table. but couldn't find something like that do you have any suggestions or immediately indexing the new node is enough? |
When a new node is added with a GPU, the Postgres database is triggered with notify_nodes_count_changed, and the node data is added. For enhancement, it will be more visible on the mainnet, and if more improvement is needed, reopen the issue. |
Update: Note: |
Current implementation:
|
Test in Progress: |
Right now we run the indexing goroutine every 1hr (it's configurable), however maybe we should also do better if the number of the nodes changes before and after? and we can even improve by indexing the newest ones first?
The text was updated successfully, but these errors were encountered: