Published: 2013-03-29 23:02:04 by Daniele Ricci

A few weeks ago I wrote a post about XMPP server performance:

The last week I spent some hours optimizing those performance issues that are indeed a critical part of Kontalk. Some optimizations include:

  • lowering log level and disabling stanza logging
  • creating JID objects only when absolutely necessary
  • using UNIX sockets among components instead of TCP/IP
  • creating stanzas by hand-writing XML in some cases
  • delaying message persistance for a few seconds, waiting for an upcoming receipt

These optimizations improved server performance a lot, especially on big numbers (e.g. roster requests).

A couple of days ago I ran some performance tests on message delivery. Rate was about 40-50 message loops per seconds1. Note that this "benchmark" was executed with both server and the only two clients running on the local host. Actually I still don't know if it's good or bad performance, given the complexity of the XMPP component architecture, overhead of XML (and Twisted) and Python. But I don't want to blame others for this :-)

  1. a "loop" is a message being sent by a client and its received receipt delivered to the sender 

Published: 2013-03-24 17:50:26 by Daniele Ricci

A few minutes ago I released Bloglooks source code to Gitorious:

Project is still in the very early stages of development, but it does give me what I need from a blogging platform, at the moment :-)

Published: 2013-03-22 15:59:32 by Daniele Ricci

300+ new users in less than 3 days.

Spreading through Twitter.

People talking on Reddit.

App downloads rapidly increasing.

Russian translation on its way.

Mailing lists are coming to life.


Visits to Kontalk websites from 20+ to more than 900!!!

That was a blast! It's so nice to see people coming when an open source project asks for help. I'm still trying to follow :-) Everything is happening so fast.