Re: new benchmarks. WAS: FreeBSD MySQL still WAY slower than Linux

2005-12-08 Thread David Xu
Greg 'groggy' Lehey wrote: I've heard this claim again and again, and I intend to look at it when I have time. I find it difficult to believe that this alone could explain the sometimes horrendous performance differences (3 to 1) that have been reported. Can somebody tell me: 1. How many cal

Re: new benchmarks. WAS: FreeBSD MySQL still WAY slower than Linux

2005-12-08 Thread Greg 'groggy' Lehey
On Friday, 2 December 2005 at 13:23:50 +1100, Michael Vince wrote: > It would be good to actually see the Linux performance on the exact same > hardware, all we ever see is how it is on FreeBSD. > > MySQL has very frequent use of queries of the system time and is > well known in FreeBSD to be slow

Re: very busy syslog server

2005-12-08 Thread Jin Guojun [VFFS]
Clear enough. em(4) should be able to handle this amount traffic without polling unless all syslog traffics come at the same time that could cause congested resource. That is why I want you to run the script to watch the CPU utilization when the drop happens. The average CPU use does NOT refle

Re: very busy syslog server

2005-12-08 Thread Jin Guojun [VFFS]
jaws wrote: What you need is more sockets available and a much larger sockbufs. Try adjusting the following parameters: net.inet.udp.maxdgram net.inet.udp.recvspace maxdgram has nothing to do with this on receiver side. If you want to play with this parameter, try to REDUCE it on sender side.

RE: very busy syslog server

2005-12-08 Thread Imri Zvik
Already tried different values, even some really high arbitrary ones... I think I will try splitting the work load on a couple of instances of syslog... I hope that would do the trick -- Imri Zvik PGP (2.6.3ia) Public Key: http://mariska.inter.net.il/~imriz/imriz.pgp -Original Message---

Re: very busy syslog server

2005-12-08 Thread jaws
What you need is more sockets available and a much larger sockbufs. Try adjusting the following parameters: net.inet.udp.maxdgram net.inet.udp.recvspace Dont rely on the default values rather set it to a much higher values. Regards, jaws Imri Zvik wrote: Hi, 1. The NIC being used is "Intel

RE: very busy syslog server

2005-12-08 Thread Imri Zvik
Hi, 1. The NIC being used is "Intel(R) PRO/1000" (the em(4) driver). 2. The CPU utilization in average is between 15% and 20%. 3. This machine is being used _only_ for the sysloging - the database resides on another server. Meanwhile, I have added some more memory to the machine, and now it has

RE: very busy syslog server

2005-12-08 Thread Imri Zvik
Hi, I have tried polling, and it did not improve the performance. Regarding the inserts - I am using delayed inserts to solve that problem exactly. I have already tried to log into files, and still had this issue... Thanks for reply :) -- Imri Zvik PGP (2.6.3ia) Public Key: http://mariska.inte