Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #28247
| Date | 2012-09-02 09:56 +0200 |
|---|---|
| From | Laszlo Nagy <gandalf@shopzeus.com> |
| Subject | Re: Async client for PostgreSQL? |
| References | <50419A55.3080904@shopzeus.com> <5042434B.3010201@thieprojects.ch> <504261E2.5030305@shopzeus.com> <50428B0A.3030403@thieprojects.ch> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.64.1346572596.27098.python-list@python.org> (permalink) |
> 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.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Async client for PostgreSQL? Laszlo Nagy <gandalf@shopzeus.com> - 2012-09-02 09:56 +0200
csiph-web