Re: CLOS persistence

On Jan 2, 8:54 am, vtail <victor.kryu...@xxxxxxxxx> wrote:
Happy New Year group,

I would appreciate comments on existing CLOS persistence libraries, in
particular elephant vs cl-perec: how reliable/fast each one is,

Elephant has a large test library to ensure reliability.

Elephant is easy to use for CLOS because of its MOP framework.


how large is the user base,

Elephant is probably the most popular.
By the way, have you looked at cl-prevalence?


how active are maintainers etc.

A bunch of knowledgeable people are on the list. Ian Eslick, the most
active one, is answering questions quickly.
There's a Trac system with a roadmap.


For elephant
in particular, I'm also interested in performance of Postgresql
backend vs BerkeleyDB.
My use case is a multi-user web-based app (I'm porting existing Perl/
MySQL application), and I would need performance that is not far worse
then that of a existing system.

IIRC the Elephant docs say that performance is best with BDB and
others are slower by a factor of three (check them out to verify
this). The only way to find out whether a given library satisfies your
performance needs is to try it. IMO the only disadvantage of Elephant
is the one cited by levy: Elephant abuses relational databases as flat
key-value-databases. But there's also a native SEXP backend in
development for Elephant.

Leslie
.