[Twisted-Python] Scaling problem

Uwe C. Schroeder uwe at oss4u.com
Thu Nov 6 23:22:14 EST 2003

Hash: SHA1

On Thursday 06 November 2003 06:14 pm, Clark C. Evans wrote:
> On Wed, Nov 05, 2003 at 09:32:23AM -0800, Uwe C. Schroeder wrote:
> | > (3. Don't use RDBMS. Use an in-process database like ZODB or Quotient's
> | > atop when it's done.)
> | >
> | :-) I'd probably do that with a web application, but even there I'll
> | : allways
> |
> | prefer a "real" database system. In process databases may be faster,
> | therefor they are less relieable and correcting errors is a virtual
> | impossibility.
> If you are using PostgreSQL, Gerhard Haring has reportedly
> made the async interface work,
> http://sourceforge.net/mailarchive/message.php?msg_id=2688514

Good link. I might start using that for some things.
For now I solved the scaling issue with an (more or less) ugly workaround. 
Since I'm using pb with  dedicated client software I made the logon a 2 step. 
The first step connects to a certain port and gets an IP-address and a port 
back. The server determines which process has the least number of clients 
connected and returns that address. That's where the client then connects for 
real work. So I now just have a bunch of twisted's running on different ports 
- - works nicely for a quickhack.
But in the long run I'll definitely have to do something about the database 
and automatic forking of more server processes.


- --
Open Source Solutions 4U, LLC	2570 Fleetwood Drive
Phone:  +1 650 872 2425		San Bruno, CA 94066
Cell:   +1 650 302 2405		United States
Fax:    +1 650 872 2417
Version: GnuPG v1.2.1 (GNU/Linux)


More information about the Twisted-Python mailing list