Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
emulating eaccelerator's "delete expired" button (ala stat once on demand)
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
_ck_  
View profile  
 More options Jan 2, 9:40 am
From: _ck_ <bbpressshowc...@gmail.com>
Date: Mon, 2 Jan 2012 06:40:01 -0800 (PST)
Local: Mon, Jan 2 2012 9:40 am
Subject: emulating eaccelerator's "delete expired" button (ala stat once on demand)
I'm switching some servers from eaccelerator to xcache as eaccelerator
has sadly fallen behind and even removed their variable data cache.

One feature I liked when running with stat off (file update checking)
was their control panel has a "delete expired" button which instead of
clearing the cache entirely, instead it does a stat on all the files
in the cache - once, on that one request, and deleted only ones with
newer files.

On a busy server with a thousand files in the cache, delete expired is
far more friendly that rebuilding 1000 opcodes, when updating just a
file or two.

I guess this could be done via the api If it's possible to examine and
delete cached files on demand  but I'd love to see a "delete expired"
right in the control panel for the next release.

I think I read somewhere that xcache doesn't even bother to store the
file timestamp info at all if stat is turned off, so that may be a
problem with this feature request. If this is true I could instead
just check for files on disk that are also in the cache and have a
timestamp that is only "x" minutes old.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
_ck_  
View profile  
 More options Jan 2, 10:49 am
From: _ck_ <bbpressshowc...@gmail.com>
Date: Mon, 2 Jan 2012 07:49:16 -0800 (PST)
Local: Mon, Jan 2 2012 10:49 am
Subject: Re: emulating eaccelerator's "delete expired" button (ala stat once on demand)
I thought I got clever and noticed xcache stored ctime which may have
been good enough to compare to the file's mtime when it was modified.

But experimenting using xcache_unset on filenames fails entirely and
xcache_clear_cache will only clear an entire memory block by id, not
individual entries by id.

So unless I am doing this incorrectly or there is an undocumented API
call, I guess this concept is completely dead in the water.

If it's impossible in 1.3.x perhaps it can be slated for 2.0

Thanks for considering.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »