|
From: Matthew R. <mr...@ca...> - 2010-02-23 00:42:34
|
Coming from a system where the Context is the main unit of management for statements, CSPO feels like the correct primary index. One question would be what effect on addition/deletion efficiency does the primary index make? More specifically, if within a transactions additions/deletions usually occur with a high number of statements per context, does the proximity of the changed statements within the primary index help performance? Matt On 2/22/2010 6:38 PM, Bryan Thompson wrote: > I would like to solicit some input on the question of whether the primary index for the quad store should be SPOC (it is today) or CSPO. There has been some discussion on this issue in the past. I am raising the issue again in the light of discussions where an entire context corresponding to a relatively large collection of statements is to be dropped, e.g., wikipedia when mapped onto a single context, and when eventual consistency is being used for the secondary indices (that is, we handle conflict resolution on the primary statement index, e.g., SPOC, and then have a restart safe protocol guaranteeing eventual updates on the secondary statement indices). > > I have come around to the opinion that mapping that much data onto a single context is generally wrong. The information would be more readily managed by mapping it onto a set of contexts corresponding to individual wikipedia entries, each of which was then associated with the source using statements about that context. > > Thoughts? > > Bryan > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > |