Re: [users@httpd] mod_*_cache on 2.0 vs. 2.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





William A. Rowe, Jr. wrote:
Forrest Aldrich wrote:

The servers have an absurd amount of RAM (8gb or more) that we could utilize for mod_mem_cache.

If that's the case, if your content is non-trivial (different reactions
to client characteristics, such as language, charset, or browser content
that varies) - I strongly recommend you allocate what you like as a ram
disk and use mod_disk_cache with 2.2.x.  It's far more robust in terms
of following all the subtleties of HTTP/1.1 caching.

If your content is trivial (doesn't vary, etc) then mod_mem_cache would
serve you just fine.


The only thing that would vary, in this case, is if the image had been updated/changed, in which case it would need to be pulled in from the backend DB. The images are 768k jpg (or less), and because it's a cache, it's disposable...

The intent here is to lessen the load on the backend DB, cache the most frequently viewed images and deliver those quickly. (ie: without using a content provider for this smaller setting).


Thanks.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux