|
If you are using an SQL backend for your AWL, Kris
Deugau gave me some ideas a few years ago where I added a column
to the AWL like such: alter table awl add column `lastupdate` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP Then I run a cron job in AWL to clear out the entries that haven't been used in a while on a gradiated scale: DELETE FROM awl WHERE lastupdate <= (now() - INTERVAL 15 day) and count < 5; DELETE FROM awl WHERE lastupdate <= (now() - INTERVAL 30 day) and count < 10; DELETE FROM awl WHERE lastupdate <= (now() - INTERVAL 60 day) and count < 20; DELETE FROM awl WHERE lastupdate <= (now() - INTERVAL 120 day); However, the idea below might be the only option for DB-Based backend. Why don't you open a ticket, please? I think it's a straightforward change and has good benefits. Might need to be a switch to control it's behavior for those who care about time more than memory, though. Regards, KAM On 4/22/2012 12:58 PM, Vitaly V. Bursov wrote: Hello, --
Kevin A. McGrail President
Peregrine Computer Consultants Corporation
703-359-9700 x50 / 800-823-8402 (Toll-Free)
![]() |
- PATCH reduce sa-awl memory usage Vitaly V. Bursov
- Re: PATCH reduce sa-awl memory usage Kevin A. McGrail
- Re: PATCH reduce sa-awl memory usage Vitaly V. Bursov
- Re: PATCH reduce sa-awl memory usage Kevin A. McGrail

