RE: comm_select.c bug

On 8 Sep 2000, at 17:11, Chemolli Francesco (USI) <ChemolliF@GruppoCredit.it> wrote:

> ...
> NAME: incoming_dns_average
> +TYPE: int
> +DEFAULT: 4
> +LOC: Config.comm_incoming.dns_average
> +DOC_NONE
> +
> ...
> +NAME: min_dns_poll_cnt
> +TYPE: int
> +DEFAULT: 8
> +LOC: Config.comm_incoming.dns_min_poll
> +DOC_NONE
> +
>
> Ehm... what are those supposed to do? When do they become relevant?

 from this data cf_parser.c is generated, which accepts and parses squid.conf
 These lines do nothing else but allows cf_parse.c to set initial defaults,
 which otherwise are left at 0, which is not what we want.
 (make clean ; make) is needed, not sure about configure.

> Also, on what hardware and what with kind of load are you seeing
> that level of CPU usage? I'm trying to gauge the good-ness
> of my setup right now.

 I just installed my new box a week ago. Dual P3-800/100 with 1GB ram.
 I'm seeing 1 cpu being constantly 100%, and the other one yawning at few %
 OS is Solaris 7, x86. Load is 6800 reqs/min with occasional peaks of 170/sec
 (async-io enabled)

 I'm somewhat in trouble justifying the purchase ;) noone can see any
 difference with older P2-450 - both are at 100% cpu.
 Thats why I'm curious whats eating up cpu.

------------------------------------
 Andres Kroonmaa <andre@online.ee>
 Delfi Online
 Tel: 6501 731, Fax: 6501 708
 Pärnu mnt. 158, Tallinn,
 11317 Estonia
Received on Fri Sep 08 2000 - 09:50:26 MDT