On Tue, Mar 6, 2012 at 9:49 AM, Paolo Castagna <[email protected]> wrote:
> I do not know your use cases and, in particular, I do not know if you > are trying to provide a faceted navigation UI on top of your TDB store. > But, from your query that seems the case. > > If those times are seconds, that is not going to provide a good user > experience to your users. ;-) > > I do not know if your store is mostly read-only with just a few, non > frequent and small updates, but if that is the case, you should really > consider putting a caching layer in front of your TDB store. > An experimental prototype Andy wrote is here: > > - https://github.com/afs/LD-Access > > A completely different alternative would be to use something such as > Apache Solr or ElasticSearch along side your TDB store, they both > support facet searches (and they can be quite fast): > > - http://wiki.apache.org/solr/SimpleFacetParameters > - http://www.elasticsearch.org/guide/reference/api/search/facets/ > > None of these options are something you get out-of-the-box though, > some work and development is involved. Thanks Paulo - caching is indeed the next thing on the list to look at :) I hadn't considered the Solr approach, but will do so. Glenn.
