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

← Older edit

Update:Archive/2.0/Architecture and General Design/Infrastructure (view source)

Revision as of 05:05, 29 April 2007

217 bytes added , 29 April 2007

no edit summary

Fligtar

canmove, Confirmed users, Bureaucrats and Sysops emeriti

1,043

edits

@@ Line 1: / Line 1: @@
-[[Update:Home_Page|Update: Home Page]] &raquo; [[Update:Architecture_and_General_Design|Architecture and General Design]] &raquo; Infrastructure
+{{AmoArchive}}
 == Introduction ==
@@ 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 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 ==
-We are using MySQL 4.0.22 for the database.  Moving forward, we will be looking at using MySQL 4.1.x in order to take advantage of subselects.  We currently have this all on one database server but moving forward we need to consider a master/slave arrangement for redundancy sake.
+We are using MySQL 4.1.7 for the database.  We currently have this all on one database server but moving forward we need to consider a master/slave arrangement for redundancy sake.
 == Web/Application Servers ==
-We are using Apache2 + PHP 4 on top of Linux machines right now.  Right now, we only have one application server and we need to fix that asap.  The current application server is running RHEL 3.
+We are using Apache2 + PHP 4 (4.3.8) on top of Linux machines right now.  Right now, we only have one application server for addons/pfs and we need to fix that asap.  The current application server is running RHEL 3.
-:Are there plans to split the extensions update service from the Application Update service since one is just static RDF files, the other is dynamic? Could the static RDF files be served from something other than Apache, perhaps a lightweight HTTPD? Perhaps not necessary if Squid was cahcing them, but I'm putting the idea out there. --[[User:Csogilvie|Csogilvie]] 12:00, 22 Jan 2005 (PST)
+The Application Update Service now lives on a separate webserver running Apache2+prefork, without the assistance of squid.  The actual update.mozilla.org domain is served from this box, too.  We discovered by trial and error (and my was it an error!) that Apache is much more efficient at handling 301/302 redirects than squid+squirm is, and that we have far less load if we just serve the RDF file from update.mozilla.org if that's the domain the client browser requests it from (which should slowly diminish as people upgrade) instead of redirecting them to aus.mozilla.org.  Requests for URIs that belong to PFS or addons are redirected to those domains.