Re: [Server-devel] ejabberd tests with old and new TLS code

2008-11-24 Thread Guillaume Desmottes
Le samedi 22 novembre 2008 à 13:17 +1300, Douglas Bagnall a écrit : > Actually hyperactivity does create fake activities, though I am not > sure to what extent it really shares them. Hopefully someone from > Collabora can explain it better (I'm interested too). Yes, it does. Fake activities are cr

Re: [Server-devel] ejabberd tests with old and new TLS code

2008-11-21 Thread Douglas Bagnall
Caroline Meeks & Martin Langhoff: >> What releases are the control setup? IS the New TLS released code? > > The 'control' setup is the ejabberd-xs package we ship for XS-0.5. The > new TLS code is a patch we could consider 'beta' quality -- there's > been no significnat QA on it. In case anyone

Re: [Server-devel] ejabberd tests with old and new TLS code

2008-11-21 Thread Martin Langhoff
Hi Caroline! > TLS = ttp://en.wikipedia.org/wiki/Transport_Layer_Security correct? Yes. ejabberd is a memory hog, and we recently discovered (hint: lots of detail in the mailing list archive) that it's only a memory hog when ssl/tls connections are used. Using ssl or tls in the xmpp protocol has

Re: [Server-devel] ejabberd tests with old and new TLS code

2008-11-21 Thread Caroline Meeks
Hi Douglas, Thank you so much for this work. We are trying to come up the learning curve on the XS and scalability and I'm sure that I care about this data. Deds and I have been contemplating these and your previous results this morning and moving ourselves up the learning curve. TLS = ttp://en.

[Server-devel] ejabberd tests with old and new TLS code

2008-11-21 Thread Douglas Bagnall
With the @online@ shared roster, I have found a small decrease in both memory and CPU consumption with the new tls code, as shown here: http://wiki.laptop.org/go/Ejabberd_resource_tests/tls_comparison This is based on these two test runs: http://wiki.laptop.org/go/Ejabberd_resource_tests/try_7 h