i don't know if you guys have looked at cache-oblivious b-trees (and
other data structures) but they seem like the new hotness.
http://supertech.csail.mit.edu/cacheObliviousBTree.html
b
On Tue, Oct 28, 2008 at 11:21 AM,
<[EMAIL PROTECTED]> wrote:
> Send elephant-devel mailing list submissions to
one (perhaps insane) idea to make an all-lisp backend easier to
implement was to leverage the underlying file system ala ZODB
directory storage, since the file system is probably using B-trees
anyways. there are fairly good architecture docs on
http://dirstorage.sourceforge.net/
tokyo cabinet lo
> > You might be better off, performance
> > wise, doing this in a C full-text indexing system and wrapping an
> > interface to it.
>
> I hadn't thought of that yet. Can you recommend any?
lucene is good, solar is a web service packaging of it, and there is a
port for common lisp (montezuma), ruby
this is an entirely anecdotal remark, not really relevant, but one of
the original inspirations for elephant was a database system that was
used in-house at a company i was at with andrew blumberg and other
lisp hackers. i was doing java crap and was a complete lisp neophyte,
and was amazed to se
Well actually not, these four tests fail: PCURSOR2, INDEXING-WIPE-
INDEX, INDEXING-REDEF-CLASS, INDEXING-TIMING.
But generally it does a good job of appearing to working well for
me. My little 3 Gigbyte data base with a half dozen classes and a
dozen indexes works quite nicely.
- ben
[
So... why is the public interface to the slot indexes limited to the
get-instance-by-* methods?
I find I'm writing routines like this:
(defun map-over-unique-values-of-slot (function class-name slot)
(ele::with-inverted-cursor (cur (find-class class-name) slot)
(loop
for count f
i wonder if these sorts of design issues for elephant newbies might be
laid out in a document or tutorial. perhaps the "blog in a minute"
tutorial can be updated to reflect your more mature codebase and
mature approaches to designing applications? or a design faq?
just an idea,
Ben
i did check out cl-store. i liked it for the most part. i think my
original reasons for not using it was because i wanted to serialize to
native arrays for use with FFI. i think this rears it's ugly head
with stuff like unicode. there may have been some other reasons i
can't entirely remember.
