Async client for PostgreSQL?
Laszlo Nagy
gandalf at shopzeus.com
Sun Sep 2 03:56:28 EDT 2012
More information about the Python-list mailing list
Sun Sep 2 03:56:28 EDT 2012
- Previous message (by thread): Async client for PostgreSQL?
- Next message (by thread): Async client for PostgreSQL?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Hmm, I was suggesting that you could replace the whole DB driver with > a webservice implemented with twisted, if you rule out threads then > with ampoule doing it with a process pool and consume this webservice > with the tornado side asynchronously. I see. I'm sorry, I misunderstood. So this would be a wrapper around PostgreSQL. Very interesting idea. (In this case, I'm not sure how to safely manage transactions.) > > production level example thread pool based DB API: > Just to give you some ballpark figures, I'm running a game server with > a daily peak of about 1500 parallel permanent connections and 50k > games played every day (avg game duration 13min, peak request > frequency close to 100req/sec) with a lot of statistics going into a > MySQL DB on US$2k worth of hardware. Twisted as basis sitting atop > FreeBSD, started the latest version in March, its running since then, > no restarts, no reboots, no problems. Thank you.
- Previous message (by thread): Async client for PostgreSQL?
- Next message (by thread): Async client for PostgreSQL?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list