Hi Anca, Daniel, >From the results of the load tests it seems the issue is directly related with >the size of presentity table:
N of presentities in Presentity table N publish msgs -> mysqld:99,9%CPU 14000 11/s 55000 6/s 180000 3/s The result is the same for tests with force_active= 1 or with xcap authorization Best regards, Toni -----Original Message----- From: Anca-Maria Vamanu [mailto:[EMAIL PROTECTED] Sent: terça-feira, 17 de Julho de 2007 12:03 To: Toni Barata Cc: devel@openser.org Subject: Re: [OpenSER-Devel] presence load tests: 1.2.1 vs trunk with mysql Hello Toni, Have you run the tests with force_active= 1 or with xcap authorization? (the generalization introduced some database query inefficiency when force_active is not set). regards, Anca Vamanu Toni Barata wrote: > Hi all, > > > > I am using MySQL 5.0.22 database for persistent storage and I have > preformed some presence load tests for publish messages, and observed > that in trunk version if I have more than 2 messages per second the > mysqld process runs out the CPU with 99,9% of his capacity. > > In the 1.2.1 version there is no such problem when performing the same > load tests. > > > > What difference between version 1.2.1 and trunk have made the mysqld > process became obsessive? > > > > Regards, > > Toni > > > > > >------------------------------------------------------------------------ > >_______________________________________________ >Devel mailing list >Devel@openser.org >http://openser.org/cgi-bin/mailman/listinfo/devel > > _______________________________________________ Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
