Re: [commits] Horde branch master updated. d5ef43754ddef15a85c9d80fccbd1923857f615c

Michael M Slusarz <[email protected]>
Newsgroups gmane.comp.horde.devel
Message-ID <20140408022827.Horde.Us1NR1U051FUTMx5mnzj-g1@bigworm.curecanti.org>
Quoting Jan Schneider <[email protected]>:

> Zitat von Michael M Slusarz <[email protected]>:
>
>> commit aa643527d85dbe874c51e21185df3c2c28bc5a42
>> Author: Michael M Slusarz <[email protected]>
>> Date:   Mon Apr 7 16:24:54 2014 -0600
>>
>>    Always use in-memory cache on top of permanent cache storage system
>>
>> framework/Core/lib/Horde/Core/Factory/Cache.php |   10 +++++++++-
>> framework/Core/lib/Horde/Core/Factory/Perms.php |    6 +-----
>> framework/Core/package.xml                      |    2 +-
>> 3 files changed, 11 insertions(+), 7 deletions(-)
>>
>> http://github.com/horde/horde/commit/aa643527d85dbe874c51e21185df3c2c28bc5a42
>
> Am I missing something or won't this completely blow up memory usage  
> of PHP processes since anything ever written or read from cache  
> during a request will be kept in memory?

What are we caching that is of any substantial size?  We are talking  
about KBs, and minimal KBs at that.  (We definitely aren't talking  
about MBs, since we have multiple cache backends that can't handle  
this e.g. memcache).

Saving a single unnecessary cache retrieval is more than worth the  
minimal memory usage to prevent it.

michael

___________________________________
Michael Slusarz [[email protected]]

-- 
dev mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.