Changes between Initial Version and Version 1 of Ticket #206


Ignore:
Timestamp:
2008-11-30T04:06:08+01:00 (5 years ago)
Author:
moo
Comment:

suexec/suphp are cgi and hurt performance already, i wonder if there's a way to overcome this. i'm not sure how much overhead they have, but yes, having XCache could still help in any case.

correct me if i get it wrong

  • shared cache, readonly by suexec-php/suphp under any user
  • private cache, accessable by current suexec-php/suphp user, reuable later even if last child for this user exits

XCache under suexec-php/suphp can request a XCache daemon to cache new php files to shared cache.

but how can XCache (told by someone?) know which should be in shared cache and which should be in private cache.

btw, XCache is able to cache files with same inode in 1 copy, and can also recognize "same content" file by using md5 algorithm in XCache 2.0. too bad that FILE is broken in either case

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #206 – Description

    initial v1  
    1313Reading might not be the problem (but world-readable is a bad thing), but the different permissions will be tricky at least in case of clearing the cache. So maybe to solve this, there has to be a daemon around that  
    1414 
    15 - owns the shared cache 
    16 - knows which directories should be cached there 
    17 - is searchable from the different fastcgi driven xcaches 
    18 - delivers shared cache content and in case of a miss for a file that has to stay in his hands: 
    19 - tells his fastcgi driven friends to store this miss at his place 
    20 - accepts new content and saves it 
    21 - will invalidate it when needed 
     15 - owns the shared cache 
     16 - knows which directories should be cached there 
     17 - is searchable from the different fastcgi driven xcaches 
     18 - delivers shared cache content and in case of a miss for a file that has to stay in his hands: 
     19 - tells his fastcgi driven friends to store this miss at his place 
     20 - accepts new content and saves it 
     21 - will invalidate it when needed 
    2222 
    2323So what do you think about that concept?