Hi Mike, to anwser you quickly.
1. I set the bandwidth limitation up to 1GB/s as well as the used cores to process the messages and the allowed stored offline messages. 2. No. Because I already had problems sending and receiving messages with 1000 chars I did not increase this parameter. Greetings, Peter ----- Original Message ----- From: [email protected] To: [email protected] Date: 03.08.2011 18:24:47 Subject: Re: Vysper performance analysis > Hello Peter, > > I was very pleased to see someone doing Vysper scalability testing. I'm with > a company called ThingWorx (http://thingworx.com) and we're currently > evaluating Vysper as an embedded messaging solution for our platform. In the > past I have had experience running ejabberd. I was hoping you could answer > two questions for me regarding your study: > > 1. Did you have any shapers configured for ejabberd during the test? I > didn't see mention of any shaping, but it could effect the results. > 2. Did you run tests with any larger message sizes? > > Thanks, > Mike > > On Aug 3, 2011, at 10:41 AM, Peter Frohberg wrote: > > > Hi all, > > > > I'm a computer scientist student at the German university TU Dresden. > > > > The past six months I wrote my minor thesis focusing on the scalibility of > > Vysper. > > > > Due the fact that the results are written in German, I tried to write a > > short summary in English, which I'd like to share and can be found here: > > > > http://www.pre-dev.de/vysper/SummaryAnalysisVysper2011.pdf > > > > If you have any questions redarding this summary, feel free to ask and I > > try my best to anwser them as detailed as possible. > > > > Greetings, > > Peter > > > > > > > > Mike Mahoney > OEM Application Specialist > ThingWorx > Office: (610) 594-6200 x817 > Mobile: (585) 314-8592 >
