Update:Archive/2.0/Architecture and General Design/Infrastructure: Difference between revisions

Line 9: Line 9:
We are currently using Squid for caching of images and content.  This has been quite scalable but we need to start considering using Apache2 + mod_cache/mod_proxy to be able to handle more types of HTTP 1.1 requests.
We are currently using Squid for caching of images and content.  This has been quite scalable but we need to start considering using Apache2 + mod_cache/mod_proxy to be able to handle more types of HTTP 1.1 requests.


We may want to consider using [http://squirm.foote.com.au/ Squirm] as part of Squid to handle certain caching situations.  See my proposal in [https://bugzilla.mozilla.org/show_bug.cgi?id=279379 bug 279379] for one. It may also be useful for load balancing.
We were using [http://squirm.foote.com.au/ Squirm] at one point as part of Squid to handle the Firefox's random string on the end of the application update URLs, to improve cacheability of the RDF files (see [https://bugzilla.mozilla.org/show_bug.cgi?id=279379 bug 279379]), however that was removed after the application update service was separated to another box.
--[[User:Luser|Luser]] 11:51, 22 Jan 2005 (PST)


Another thing to consider might be [http://www.danga.com/memcached/ Memcached], to see if that would help? --[[User:Csogilvie|Csogilvie]] 12:06, 22 Jan 2005 (PST)
The addons and plugin-finder sites are now the only ones living behind our dual squid servers.
 
:Another thing to consider might be [http://www.danga.com/memcached/ Memcached], to see if that would help? --[[User:Csogilvie|Csogilvie]] 12:06, 22 Jan 2005 (PST)


== Database ==
== Database ==
Confirmed users, Bureaucrats and Sysops emeriti
674

edits