Aaron Stone wrote:
Hmm, yeah, true, no decision yet, but lots of excitement ;-) However,
there are some things that simply need to be threaded. Afaict, Oracle's
connection overhead is so huge that nothing getting near it can survive
without threading. I'd like to see some of that with my own eyes, but I'm
confident that the numbers I have read over the years aren't entirely off
base.
Could you please explain how Oracle's connection overhead directly
translates to we need threads? A new thread still has to open up a new
connection to the DB. It sounds to me that Oracle's connection overhead
(or Postgresql or whatever) is more an argument for persistent
connections and pre forking more than threads. But if I'm missing
something please let me/us know.
