在shelve和sqlite之间选择真正的大字典(Python) [英] Selecting between shelve and sqlite for really large dictionary (Python)
问题描述
。我正在考虑使用格式为
vector_key,element_no,value
的细粒度结构来帮助有效的分页,而不是将所有10k个矢量的元素存储到同样的记录。我真的很感谢任何关于这个问题的建议。你想要sqlite3,那么如果你使用ORM,如 sqlalchemy ,那么您可以轻松地扩展并使用其他后端数据库。
另外您正在谈论的一点叫做归一化,我个人从来没有很好在其中此应该为您解释。
正如额外的注释一样,此显示搁置vs sqlite3中的性能失败
I have a large Python dictionary of vectors (150k vectors, 10k dimensions each) of float numbers that can't be loaded into memory, so I have to use one of the two methods for storing this on disk and retrieving specific vectors when appropriate. The vectors will be created and stored once, but might be read many (thousands of) times -- so it is really important to have efficient reading. After some tests with shelve module, I tend to believe that sqlite will be a better option for this kind of task, but before I start writing code I would like to hear some more opinions on this... For example, are there any other options except of those two that I'm not aware of?
Now, assuming we agree that the best option is sqlite, another question relates to the exact form of the table. I'm thinking of using a fine-grained structure with rows of the form vector_key, element_no, value
to help efficient pagination, instead of storing all 10k elements of a vector into the same record. I would really appreciate any suggestions on this issue.
You want sqlite3, then if you use an ORM like sqlalchemy then you can easily grow to expand and use other back end databases.
Shelve is more of a "toy" than actually useful in production code.
The other point you are talking about is called normalization and I have personally never been very good at it this should explain it for you.
Just as an extra note this shows performance failures in shelve vs sqlite3
这篇关于在shelve和sqlite之间选择真正的大字典(Python)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!