写优化、无锁、日志结构的索引?
Write optimized, lock free, log structure index?
Azure 的 DocumentDB 有一个写入优化的 JSON 数据存储,具有记录的自动索引。是否有很好的资源来了解这是如何实现的?这在学术数据库文献中有详细记录吗?
DocumentDB 将索引策略描述为:
Automatic indexing of documents is enabled by write optimized, lock free, and log structured index maintenance techniques. DocumentDB supports a sustained volume of fast writes while still serving consistent queries.
http://azure.microsoft.com/en-us/documentation/articles/documentdb-indexing-policies/
还声称此索引通常需要主索引大小的 2-20% table:
Based production usage in consumer scale first party applications using DocumentDB, the typical index overhead is between 2-20%. The indexing technology used by DocumentDB ensures that regardless of the values of the properties, the index overhead does not exceed more than 80% of the size of the documents with default settings.
http://azure.microsoft.com/en-us/documentation/articles/documentdb-manage/#IndexOverhead
是否有任何论文描述了如何实现这种索引方案?
还没有论文。
一篇描述我们索引内部结构的论文已经起草,正在接受最终审查。
我们希望在最终定稿后尽快发布。
Azure 的 DocumentDB 有一个写入优化的 JSON 数据存储,具有记录的自动索引。是否有很好的资源来了解这是如何实现的?这在学术数据库文献中有详细记录吗?
DocumentDB 将索引策略描述为:
Automatic indexing of documents is enabled by write optimized, lock free, and log structured index maintenance techniques. DocumentDB supports a sustained volume of fast writes while still serving consistent queries.
http://azure.microsoft.com/en-us/documentation/articles/documentdb-indexing-policies/
还声称此索引通常需要主索引大小的 2-20% table:
Based production usage in consumer scale first party applications using DocumentDB, the typical index overhead is between 2-20%. The indexing technology used by DocumentDB ensures that regardless of the values of the properties, the index overhead does not exceed more than 80% of the size of the documents with default settings.
http://azure.microsoft.com/en-us/documentation/articles/documentdb-manage/#IndexOverhead
是否有任何论文描述了如何实现这种索引方案?
还没有论文。 一篇描述我们索引内部结构的论文已经起草,正在接受最终审查。 我们希望在最终定稿后尽快发布。