Peter, a few questions,

use SWISH::API::Stat;
          my $swish = SWISH::API::Stat->new(
                            log             => $filehandle,
                            indexes         => [ 'path/to/index' ],
                            paranoia_level  => 1
                            );


is log needed? I am pretty cautious about how much logging i do on my 
production boxes, a bare minimum is the rule...

currently, we scp the indexes into and incoming folder, mv them into 
place, and reload apache. This worked for a while, but as our volume of 
searches has increased, this is where we end up with stale index 
filehandles and evergrowing httpd processes, so now we apachectl stop; mv 
index; apachectl start; With SWISH::API::Stat, do you recommend a reload 
after the indexes are copied into place?

regards,

Brad
---------------------
Brad Miele
VP Technology
IPNStock.com
866 476 7862 x902
bmiele@ipnstock.com

On Mon, 6 Nov 2006, Peter Karman wrote:

>
>
> brad miele scribbled on 11/6/06 11:16 AM:
>> Peter,
>>
>> Sorry if this has been reviewed already. I want to put SWISH::API::Stat
>> into place on my mod_perl servers as I am suspecting index swapouts as a
>> cause of some crazy load spikes that we have been seeing.
>>
>> Is the move from SWISH::API 0.03 to SWISH::API 0.04 pretty painless, ie.
>> any big changes?
>>
>
> no big changes, really. Mostly usability things: the perlized method names, and
> a bug fix for Fuzzify() (iirc).
>
> Make sure you get the latest SWISH::API::Stat (and SWISH::API::More) from CPAN,
> as the latest version (0.03) is a must-have for mod_perl.
>
>
>
> -- 
> Peter Karman  .  http://peknet.com/  .  peter(at)not-real.peknet.com
>
>