W3C home > Mailing lists > Public > public-rdf-ruby@w3.org > March 2011

Fwd: rdf.rb/spira bulk read question

From: Gabor Ratky <gabor@secretsaucepartners.com>
Date: Wed, 2 Mar 2011 16:35:48 +0100
To: public-rdf-ruby@w3.org
Message-Id: <9BCA5906-1CDC-4DA6-9562-6782EB409545@secretsaucepartners.com>
Greg,

as soon as I sent my email, I saw that you have been actively committing to the project since january ;) We do extensive work with CouchDB (along with couchdb-lucene) so I can try to elaborate on my previous comment after looking at rdf-couchdb more closely. Definitely wouldn't want to bash something without intimate knowledge, I just shared my initial impression. 

Best,
Gabor

Begin forwarded message:

> From: Gabor Ratky <gabor@secretsaucepartners.com>
> Date: March 2, 2011 4:31:54 PM GMT+01:00
> To: Greg Lappen <greg@lapcominc.com>
> Cc: public-rdf-ruby@w3.org
> Subject: Re: rdf.rb/spira bulk read question
> 
> Are you using Dan Thomas' rdf-couchdb project? (https://github.com/ipublic/rdf-couchdb) I've found the project a naive RDF::Repository implementation on top of CouchDB in many ways. Great proof of concept with rdf-spec tests passing, but definitely needs work, especially in the 'efficient querying' space, IMHO.
> 
> Are you taking a hard dependency on CouchDB in other parts of your architecture (like us), or just chose it as an RDF repository?
> 
> Gabor
> 
> On Mar 2, 2011, at 3:20 PM, Greg Lappen wrote:
> 
>> Hi all,
>> 
>> We are making good progress with our project, and I've gotten to the point where I am storing datasets in our rdf repository (rdf.rb based, implemented on couchdb).  Now I'm building a page that allows the data to be exported in various formats (xml, csv, etc), but when I iterate over all of the data, it is extremely slow.  I see Spira querying the repository once for each instance when I iterate using the model's "each" method.  I understand why, I'm just wondering if there's a faster way to query all of the instances of a Spira class.  One thought we had was to use a graph query instead, which would pull out all the properties in N queries (where N is the number of properties in the class).  In the example I'm trying, this would be 23 queries, which is better than hundreds or thousands of queries. Is this as good as it gets?  I'm accustomed to working with RDBMS and ActiveRecord, so I may just have to shift my expectations a bit, but thought I would ask the group if there's something I'm missing....thanks as always,
>> 
>> Greg
> 
Received on Wednesday, 2 March 2011 15:36:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 2 March 2011 15:36:38 GMT