-
Notifications
You must be signed in to change notification settings - Fork 674
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
Dynamic graph without need of max_elements #172
Comments
Hi @ashfaq92, This can be automatized by extending the index once it hits the capacity by making a copy of index's working memory. Also, On the downside, it seems that doing so would require to halt the index during the operation with a dedicated shared lock. I think that should be possible to implement it via a wrapper of the python API. C++ version might be a much better solution, but 1) it would require a shared lock, which is C++14 (not sure if it is a big problem). 2) might cause some slowdown (not sure if a big problem either, as the lock can be acquired only once per search/insertion). |
I can guide through the process if you want to implement that. |
Hi @yurymalkov, |
Hi, thanks for great work.
In some domains, the size of graph is not know in advance. Each time a node is created and should be added into graph. In other words, graph should dynamically adjust the new nodes. One solution can be: giving graph maximum affordable size i.e.
max_elements= sys.maxint
. But this costs huge time and space overhead in indexing process. While in real workflow the nodes can be only 1000. Let suppose we don't know the number of nodes (max_elements) in advance, then how to use this library to solve this problem? What are limitations that require that max_elements should be specified in advance? It would be charming if we don't have to specify max_elements in advance. If there are some programing limitations, please describe so that we can collaboratively find the solution. If it is impossible, please share some work_around/hacks to deal with this problem.The text was updated successfully, but these errors were encountered: