Hi Tomasz, Thanks for your reply. The problem appears to be related syslog. If I turn of syslogd, the problem is gone. If I configure all jabberd2 components to log to file instead of syslog, the problem is also gone. I don't know why changing mysql from unix socket to tcp/ip would make syslog behave differently, but at least now it works for me :)
- Michiel On 9/13/07, Tomasz Sterna <[EMAIL PROTECTED]> wrote: > > Dnia 12-09-2007, Śr o godzinie 17:25 -0700, Michiel Frishert napisał(a): > > I changed the sm.xml configuration to use an IP rather than > > localhost, and suddenly there is a huge drop in performance. I can't > > get more than a couple hundred concurrent users. > > [...] > > I've run the mysql benchmarking programs and performance is nearly > > the same with TCP or unix socket, which suggests to me there's > > something wrong with my jabberd setup. > > > > Any suggestions as to what might be going on? > > I do not have experience with MySQL backend. > Frankly, I did not use it in years now... > > But, if you could find out what is wrong, or could provide patches - I > would gladly integrate it in. > > > > -- > Tomasz Sterna > Xiaoka.com http://www.xiaoka.com/ > > _______________________________________________ > Jabberd2 mailing list > [email protected] > http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com >
_______________________________________________ Jabberd2 mailing list [email protected] http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
