I don't have an exact answer, but I can give you a starting point - It's my understanding that with the datastax driver/api, there is a large initial connection hit, and most people want to re-use the same same Session across multiple requests to minimize that. It looks like a popular strategy is to use a @postfork hook to set up the connection in each worker.
Depending on how you're going to deploy (uwsgi, gunicorn, etc) there are slightly different strategies to initializing a session/connection pool for each worker. that sort of stuff isn't really pyramid specific, so there is a lot of information on it. Not an exact answer, but I was looking into this a few months ago and that's as far as I got. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
