Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #28247 > unrolled thread

Re: Async client for PostgreSQL?

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Async client for PostgreSQL? Laszlo Nagy <gandalf@shopzeus.com> - 2012-09-02 09:56 +0200

#28247 — Re: Async client for PostgreSQL?

> 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.

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web