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 created, joined used and left
randomly.


G.

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


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.wikipedia.org/wiki/Transport_Layer_Security  correct?

When you test old and new TLS there are code changes on both XO and XS?

What releases are the control setup?  IS the New TLS released code?

Questions about the methodology.


   - 1 connection models 1 user?
   - Does it just connect?  does it share any activities? would sharing
   activities affect the outcome in XS in any way?
   - Have you tested with current shared roaster vs a roster grouping system
   that only allows say 30 or 50 people in any online users roaster at once?
   If not do you expect that to be an important factor?

Thanks,
Caroline  Deds



On Fri, Nov 21, 2008 at 5:34 AM, Douglas Bagnall [EMAIL PROTECTED]wrote:

 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
 http://wiki.laptop.org/go/Ejabberd_resource_tests/try_6

 which can be found in raw form, and converted into graphs via the
 next two links:

 http://dev.laptop.org/~dbagnall/ejabberd-tests/http://dev.laptop.org/%7Edbagnall/ejabberd-tests/
 http://dev.laptop.org/git?p=users/dbagnall/ejabberd-tests.git

 These are different tests than the one I reported a few weeks ago,
 which was conducted without the shared roster.  Evgeniy asked if I
 could repeat that test with SMP disabled, but it happens that I can't
 because I've lost one of the computers that ran the clients.  I could
 re-run this one without SMP if that was likely to be interesting.

 It looks like the cost of @online@ shared roster outweighs the cost of
 TLS.  That's about as insightful as I get at this time of night.


 douglas
 ___
 Server-devel mailing list
 Server-devel@lists.laptop.org
 http://lists.laptop.org/listinfo/server-devel




-- 
Caroline Meeks
Solution Grove
[EMAIL PROTECTED]

617-500-3488 - Office
505-213-3268 - Fax
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


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 the advantage of using compression -- that's why we use
it.

 When you test old and new TLS there are code changes on both XO and XS?

Only XS. Recently, Process One (developers of ejabberd) published a
patch that promised to reduce the mem usage on the server. Douglas and
others are comparing before-and-after -- the P1 guys say it saves a
lot of mem, independent testing is showing a mix.

 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.

 Questions about the methodology.

In general - there are good notes on all of this in the archives of this list.

 1 connection models 1 user?

yes - it's a script called hyperactivity... more in the archive.. ;-)

 Does it just connect?

yes

 does it share any activities?

no but part of the test is to share activities using real XOs in
parallel to hyperactivity being used.

 activities affect the outcome in XS in any way?

Not much on the XS, but yes on the bandwidth / spectrum used. Joe (QA
team) has posted about his experimental results on this.

 Have you tested with current shared roaster vs a roster grouping system that
 only allows say 30 or 50 people in any online users roaster at once?  If not
 do you expect that to be an important factor?

We don't have that yet -- as I mentioned at Sugarcamp, we're working
on it based on mod_roster_odbc, postgres and moodle. And yes, we
expect it to be a big factor, otherwise we'd do something else ;-)

cheers,


m
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


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 does want to try it, the packages I used are

patched: http://dev.laptop.org/~dbagnall/ejabberd-xs-2.0.1-12.fc9.olpc.src.rpm
unpatched: http://dev.laptop.org/~dbagnall/ejabberd-xs-2.0.1-11.fc9.olpc.src.rpm

 yes - it's a script called hyperactivity... more in the archive.. ;-)

 Does it just connect?
 does it share any activities?

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).

Douglas
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel