Just to close my question:
I tweaked few settings for innodb and seems pretty good already.
The biggest is being: transaction_isolation = READ-COMMITTED
Of course not for everyone but for my needs, this works perfectly.
thanks
On Thursday, June 27, 2013 8:36:51 PM UTC-7, Srini wrote:
I
I guess my question should have been how do I handle consistent non locking
reads as app server is reverse proxied and each request goes to different
session.
thanks
On Thursday, June 27, 2013 8:11:38 PM UTC-7, Srini wrote:
Hi,
I am using tornado, sqlalchemy behind ngnix in reverse proxy
Thanks for pointing me there, Michael. Wasn't aware of that InnoDB
feature. Make all sense, now.
On Aug 13, 12:37 am, Michael Bayer mike...@zzzcomputing.com wrote:
On Aug 12, 2010, at 7:36 AM, Erich Eder wrote:
I've found a strange behaviour when using multiple sessions: A
committed change
