thanks for your suggestions two clear options 1) agents and queued transactions 2) MVC enabled databases (postgresql, h2 (neat project))
Ill try the first option and see how it scales, and worst case move to the second Thanks again Scott On Mar 25, 12:47 pm, prhlava <prhl...@googlemail.com> wrote: > > Is it as simple as moving to a better database, such as > > mySQL? > > PostgreSQL is considerably better (even than MySQL, which still uses > locks AFAIK) > for anything concurrent. The PostgreSQL is using multiple version > concurrency (MVC) > approach - the same approach the clojure STM is using. > > The PostgreSQL might need a bit of tuning (the defaults are very > conservative), > but after that it usually performs very well. Make sure that you > understand the > PostgreSQL transactions and how they work, but usually - in default > settings, the > readers do not block writers, and readers always see consistent view > of the data > (but this view could be a "bit behind" in terms of time). > > The PostgreSQL mailing list is both, friendly and knowledgeable - > speaking from > experience. > > Kind regards, > > Vladimir -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en To unsubscribe from this group, send email to clojure+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
