libpurple in server

[Ethan Blanton]

Christopher Baus spake unto us the following wisdom:
> > So, while this is true at some level, you should be able to handle an
> > awful lot of IM connections before this becomes a problem.  Most of
> > your I/O will be simple buffer reads and writes, and the only real
> > cost you'll pay is the system call overhead.  (Disk I/O in libpurple
> > is about the only thing which might degenerate into something other
> > than a buffer read or write, as it is blocking.)
> 
> Sorry, when I said I/O, I meant disk I/O.  For where I'm at right now,
> disk I/O  performance is fine, but I expect this to be the first
> bottleneck I run into.

Fortunately, this is pretty easy to fix, and completely unrelated to
the threaded-ness of libpurple.  We do disk accesses in a *very* small
number of well-contained places.

Ethan

-- 
The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://pidgin.im/pipermail/devel/attachments/20070601/9f33eff9/attachment.sig>