Stuart Henderson s...@spacehopper.org writes:
Hello again,
after a bit of searching, I am not sure that the datasize limits imposed
in login.conf for the default class override the datasize for the daemon
class in case of named.
There is an extra restriction for cache size in BIND itself. From
Stuart Henderson s...@spacehopper.org writes:
Hi Stuart,
Also ps(1) output seems to confirm that named process limit is the
entire memory of the machine.
root@openbsd: /var/named/tmp # ps -ax -v | head
PID STAT TIME SL RE PAGEIN VSZ RSS LIM TSIZ %CPU %MEM
COMMAND
31077 S
Stuart Henderson s...@spacehopper.org writes:
On 2012-04-20, Kostas Zorbadelos kzo...@otenet.gr wrote:
Just discovered that under Linux bind seems to use 5 threads (2
processors). Under the same VM config on OpenBSD bind seems to have
no threads (using T under top(1)).
In 5.0 and 5.1
On 2012/04/21 11:54, Kostas Zorbadelos wrote:
In -current this has changed however in OpenBSD BIND is built without
threads anyway.
Doesn't this affect BIND's performance?
Anyway, a stress test will tell...
Untested but in 5.1 and earlier I doubt you will see an improvement with
threads,
On 2012/04/21 11:51, Kostas Zorbadelos wrote:
Thanks for the good explanations.
I always start bind either at system boot, or manually under the root
user using the rc.d script. Therefore the class should be daemon
according to your explanations and from what I see in
/etc/rc.d/rc.subr.
Hello all, sorry for the big mail that follows.
These are my first attempts at fine tuning and stress testing in OpenBSD
so excuse my ignorance.
I am stress testing BIND as a resolver on Linux (CentOS 6) and OpenBSD
(5.0 release). I will evaluate unbound since this will be included
in base also
On 2012-04-20 07:43, Kostas Zorbadelos wrote:
I understand the kernel VM layers are completely different, but how come
the named process on OpenBSD for the same load consumes so low resident
memory? Also, why VZS RSS on OpenBSD?
The general question I am trying to answer is, can BIND utilize
On Fri, Apr 20, 2012 at 02:43:05PM +0300, Kostas Zorbadelos wrote:
Hello all, sorry for the big mail that follows.
These are my first attempts at fine tuning and stress testing in OpenBSD
so excuse my ignorance.
I am stress testing BIND as a resolver on Linux (CentOS 6) and OpenBSD
(5.0
Otto Moerbeek o...@drijf.net writes:
You neglect to tell us platform details so we cannot tell.
I mentioned
trying to fill as much as I can in BIND's cache and I use 2 VMs with
identical configuration (2 CPUs, 8GB RAM) for the systems to perform the
tests.
more details:
Simon Perreault simon.perrea...@viagenie.ca writes:
On 2012-04-20 07:43, Kostas Zorbadelos wrote:
Hi Simon,
I understand the kernel VM layers are completely different, but how come
the named process on OpenBSD for the same load consumes so low resident
memory? Also, why VZS RSS on OpenBSD?
On 2012-04-20 14:07, Kostas Zorbadelos wrote:
Eventually you are right. However I am trying to answer the primitive
question: should I buy servers with a lot of RAM or not? If BIND cannot
utilize more than 4GB let's say, it makes no sense to buy servers with
32GB. The servers' only role will be
Simon Perreault simon.perrea...@viagenie.ca writes:
Here's a test protocol for you:
1. Set your VM to 6G.
It is set to 8GB.
2. Set max-cache-size to 4G.
3. Measure how many records it can store.
I didn't have a way to see that but just found
rndc dumpdb -cache :)
Do you have any other
On 2012-04-20, Kostas Zorbadelos kzo...@otenet.gr wrote:
Also, per process limits play a role.
Does named has such a limit by default?
OpenBSD has a limit by default, see login.conf(5). Daemons started
when the system is booted or using /etc/rc.d scripts typically use
the class 'daemon'.
Stuart Henderson s...@spacehopper.org writes:
On 2012-04-20, Kostas Zorbadelos kzo...@otenet.gr wrote:
Also, per process limits play a role.
Does named has such a limit by default?
OpenBSD has a limit by default, see login.conf(5). Daemons started
when the system is booted or using
Just discovered that under Linux bind seems to use 5 threads (2
processors). Under the same VM config on OpenBSD bind seems to have
no threads (using T under top(1)).
Is this part of the patches in the OpenBSD version of BIND?
Regards,
Kostas
--
Kostas Zorbadelos
On 2012/04/20 22:44, Kostas Zorbadelos wrote:
Stuart Henderson s...@spacehopper.org writes:
On 2012-04-20, Kostas Zorbadelos kzo...@otenet.gr wrote:
Also, per process limits play a role.
Does named has such a limit by default?
OpenBSD has a limit by default, see login.conf(5).
Stuart Henderson s...@spacehopper.org writes:
On 2012/04/20 22:44, Kostas Zorbadelos wrote:
Stuart Henderson s...@spacehopper.org writes:
On 2012-04-20, Kostas Zorbadelos kzo...@otenet.gr wrote:
Also, per process limits play a role.
Does named has such a limit by default?
On 2012-04-20, Kostas Zorbadelos kzo...@otenet.gr wrote:
Stuart Henderson s...@spacehopper.org writes:
On 2012/04/20 22:44, Kostas Zorbadelos wrote:
Stuart Henderson s...@spacehopper.org writes:
On 2012-04-20, Kostas Zorbadelos kzo...@otenet.gr wrote:
Also, per process limits play a
On 2012-04-20, Kostas Zorbadelos kzo...@otenet.gr wrote:
Just discovered that under Linux bind seems to use 5 threads (2
processors). Under the same VM config on OpenBSD bind seems to have
no threads (using T under top(1)).
In 5.0 and 5.1 threads are entirely done in userland and won't show
19 matches
Mail list logo
