Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <434A7AA8.5040704@apache.org>
Date: Mon, 10 Oct 2005 16:28:56 +0200
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [QVote] Configurable default for sitemap reloading
References: <434A5AA9.8040708@apache.org> <434A6040.1080806@apache.org>
 <434A67D4.3090704@apache.org> <434A6C46.90002@apache.org>
 <5DEB29FD-A31F-4706-B0D2-66DF9F6AA8E5@apache.org>
In-Reply-To: <5DEB29FD-A31F-4706-B0D2-66DF9F6AA8E5@apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Torsten Curdt wrote:

> 
> IMO this is FS ...as long as the file system checks are cached the  
> impact is
> sooooo minimal that even on high-load production system it should not  
> really
> matter to much ...and we got rid of another option (that probably  
> nobody has
> really used anyway because everyone is too lazy to turn it back on  
> for every
> little change on the production system)
> 
> ...or am I really mistaken?
> 
Yes :) We always (ok, let's say to 95%) turn off the reload check - I
don't measured the real impact, but it's evident that checking consumes
time, we had to add the delayed source to make it work under load. So,
if you can't turn it off, this might mean that you have to increase the
delay if the load gets higher, I think.
Turning off and turning on reload checking is really a pita right now;
it gets soo easy with one switch. So this might be a chicken-egg
problem. As it is so difficult, noone really used it?

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/