Well, this is certainly interesting, since this would allow me to
decouple the storage system from the lisp environment allowing the
possibility of setting up a cluster of lisp machines to handle
application logic. Isn't there a way to achieve this on BDB?
We prefer to deploy our systems on clusters of "inexpensive" machines
in order to leverage hardware failures and it seems that scalability
of BDB/Lisp applications is achieved by scaling a single machine.
Now, postmodern being 4x slower could be an issue. However, how does
that compare to a regular CL-SQL and relational queries is a different
story. If postmodern is about the same speed as hitting Postgres with
CL-SQL and just using plain SQL instead of elephant, at the end of the
day, that's the performance our users are getting anyway :)
Thanks,
Waldo
Since Postgres does allow for features such as replication,
clustering, and fail-over with multiple active simultaneous client
connections, does this mean that I could have multiple (separate)
lisp clients using elephant connecting to a separate Postgres
cluster with no concurrency issues?
Yes.
You can do this on BDB, but only on the same system as it relies on
shared memory locks between processes. This helps for multi-CPU
systems (one lisp process per CPU) but not for distributing Elephant
across
Thanks,
Waldo
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
