From owner-freebsd-arch@FreeBSD.ORG Thu May 4 17:28:39 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D162B16A405; Thu, 4 May 2006 17:28:39 +0000 (UTC) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id C98FC43D48; Thu, 4 May 2006 17:28:38 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from jersey ([80.80.97.196]) (authenticated bits=0) by mail.r61.net (8.13.6/8.13.6) with ESMTP id k44HSExI078924 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 4 May 2006 21:28:24 +0400 (MSD) (envelope-from bushman@rsu.ru) Message-ID: <019f01c66fa0$34052240$a9655050@jersey> From: "Michael Bushkov" To: "Ceri Davies" , "Robert Watson" References: <002401c66b0a$44c230e0$01655050@jersey> <44529510.6030704@freebsd.org> <20060428222627.GI51777@submonkey.net> <001801c66b42$d48d4740$e8775050@jersey> <20060429100236.GJ51777@submonkey.net> <20060429174129.H11416@fledge.watson.org> Date: Thu, 4 May 2006 21:28:25 +0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on asterix.r61.net X-Virus-Status: Clean Cc: freebsd-current@FreeBSD.org, Hajimu UMEMOTO , Colin Percival , freebsd-arch@FreeBSD.org Subject: Re: [HEADS UP] upcoming /etc/services updating X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 17:28:39 -0000 Hi, > Robert Watson wrote: > BTW, since this is in the context of significantly increasing the size of > the services database, have we: > > (1) Measured what impact adding the cache daemon for local databases has? > Specifically, does adding the cache daemon for a database like > /etc/services, /etc/passwd, etc, improve performance, or add overhead? > > (2) Looked at adding /etc/services.db, similar to the other compiled > database > pieces, in order to improve lookup times for very large tables. This > change would be orthoganal to a cache daemon. getpwXXX() and getgrXXX() functions work slower in about 3 times with cached enabled when only "files" source is used. The thing is, I think, I'll be able to improve cached's performance to reduce this drawback. Currently, cached gives real performance gain with sources such as DNS and LDAP and is not that useful with local sources, except the "services" database (I'll do accurate benchmarking with all types of sources and will post the report with its results). I'll test the cached performance with very large /etc/services file. However, at this moment, the solution with compiled database for services will be probably faster. Anyway, cached can be used right now to allow IANA list importing without significant performance drawbacks, IMHO. With best regards, Michael Bushkov