From: Lars MLLER (lmuelle_at_SuSE.de)
Date: Tue Jan 11 2005 - 11:30:35 CET
Date: Tue, 11 Jan 2005 11:30:35 +0100 From: Lars MLLER <lmuelle@SuSE.de> Message-ID: <20050111103035.GA28990@gray.suse.de> Subject: Re: [suse-sles-e] bind 9.3.0 performance problem on x86 Linux
On Tue, Jan 11, 2005 at 05:56:01PM +0800, lunardancer wrote:
> In my testing enviroment x86 Suse Linux is having trouble in 4 CPUs
> config, I'd summary below, hope you could help.
> I use queryperf, which is included in bind, to test bind 9.3.0
There is no BIND 9.3.0 on SLES 9. SLES 9 includes BIND 9.2.3. As 9.3.0
must be a self compiled binary we can't provide much help.
Do you realy need 9.3.0? Please provide arguments why you can't stay
with the SLES 9 version.
> performance on Linux(sles9), both HP Proliant(dl580 G2) and
> Itanium(rx4640). This is just a simple test, only 5 records in a
> master domain, so all data are in cache. named is compiled and
> configured to enable multi-threads. I use 4 queryperf clients, add
> presure to a simgle server (4 IPs over a single NIC) separately.
> For Integrity Linux(2.4), 2 cpu got ~50000 qps, and 4 cpu got ~75000.
> usr% is about 70%, sys% is below 30%.
> I suppose this is ok.
> For Proliant Linux(2.4), 2 cpu got ~50000 qps, but 4 cpu got almost
> also 50000. sys% is 40%, user 40%, softirq 10%.
SLES 9 is kernel 2.6 based. Which version are you running?
cat /etc/SuSE-release
> Network is not a problem, since rx4640(4cpu) took 15MB/s, which
> dl580(4cpu) only took 11MB/s.
> I suspect either the suse kernel has a scalability problem, or x86
> architecture has trouble handling mass dns requests.
> /etc/init.d/named only added a -n 4 option
Don't edit the init script. You'll lose your changes with an update.
Use NAMED_ARGS of /etc/sysconfig/named instead.
Doersn't BIND detect the four CPUs automatically?
Lars Müller
-- Lars MÜLLER [ˈlaː(r)z ˈmʏlɐ] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
This archive was generated by hypermail 2.1.7 : Tue Jan 11 2005 - 11:30:44 CET