From: Lionel B. <lio...@bo...> - 2004-12-16 16:20:40
|
David Rees wrote the following on 12/16/04 16:56 : > Rene Joergensen wrote, On 12/16/2004 3:25 AM: > >> - Cleaning from cron, calling sqlgrey with --db-clean (or seperate >> perlscript (but that would mean more code to maintain)), this is in my >> eyes a pretty flexible way, and non-blocking without rewriting SQLgrey >> to use Net::Server::Prefork, and then just tell SQLgrey that cleaning >> is done externally, and it doesn't have to worry about it. Default >> should be one of the other ways, to avoid people who doesn't RTFM >> complaining about large databases. > Remember that even with Multiplex you can fork early to launch another process which can do the asynchronous cleanups. You won't have to maintain cron entries this way. > > I think this one is a great idea. I don't see the need for cleaning > out the database maybe more than once every hour or so, and being able > to move the cleanup process outside of the main sqlgrey process will > reduce the latency hit of having the daemon itself do cleanup. Not a > big deal in your typical setup, but it will make a big difference in > high volume setups. Sure. I wonder how SQLite will react to this though... I'm not sure it won't lock the whole table or worse the database when doing the DELETE. That will be 1.6 material, I need to think about this a little more and test things. In the mean time 1.4.1 will be released with a configurable "cleanup_delay" (better describes what the current maint_delay internal variable does) with a default set to 30 minutes. Best regards, Lionel. |