On Thu, Feb 21, 2008 at 3:35 PM, John DeSoi <[EMAIL PROTECTED]> wrote: > > On Feb 21, 2008, at 6:12 AM, Alex Mizrahi wrote: > > > elephant reads/writes slots individually, so this means we cannot > > have more > > than 1000-10000 slots operations per second. that sounds quite > > prohibitive. > > So with an SQL engine this translates to one SELECT/INSERT/UPDATE per > slot value read or write? Are you using transactions and prepared > queries with PostgreSQL? That might help some, but as you say it > probably won't scale up very well
We use prepared queries for select and a stored procedure for inserts and updates, within transactions. Tables are indexed. As explained, the bottleneck is probably communication overhead and context switching rather than database performance. /Henrik _______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
