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 =
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
Martin Langhoff wrote:
http://wiki.laptop.org/go/Ejabberd_resource_tests/tls_comparison
The graphs all have different y scales, which makes them hard to
compare. Can you fix them easily to all be with the same y scale? Or
put a big blinking warning -
I've taken out the minimum graphs for
On Fri, Nov 21, 2008 at 6:54 PM, Douglas Bagnall
[EMAIL PROTECTED] wrote:
Martin: some of my earliest tests were suggesting peaks over 1MB per
connection, which might be the source of the confusion. But for those
I probably *did* have the shared roster on, though because I was
unaware that
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 does
