(Takes me back to the heyday of SQL, when one thread would start a long transaction, which the db would establish as a full-table lock, and nothing else could get done until the transaction committed.)
Another thing you could do is decouple the periodic bulk procedure from the web app and run them in separate OS processes. You could more easily turn off the bulk procedure, change the way it is triggered, move it to another computer so the website could run on a Raspberry Pi, load-balance the website among 99 servers, or reimplement the bulk procedure a different way and choose between them. -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
