Yeah, this isn't really a rails question. However, you should look at using something like Varnish http://varnish-cache.org/ to serve the static files.
On Sep 1, 8:59 am, Mohit Sindhwani <[email protected]> wrote: > Hi All, > > We are building a maps based site in which we serve out map tiles > created by us. The entire application is working well enough and we > have followed through on most of the best Rails practices to speed up > things. We have also now gone through the list of YSlow and typical > HTTP practices to further reduce the time spent in the application. > > I guess it's now time to go beyond the design and look at what can be > done with the servers. We are using a traditional Apache + Mongrel > Cluster for deployment at this time. > > I have been reading and Thin looks attractive, as do Nginx and > Lighttpd. I am wondering what we should look at next. > > Serving map data requires us to server a number of tiles (256 x 256 > pixels each) to create the map the user sees. Naturally, we will add > "expires" headers, etc. so that the client caches it (if it can). We > are just wondering if there is a recommended way to reduce the time it > takes to serve files. > > The tiles are served from a complex directory structure on four assets > domains. Is there a "very fast static file server" that you would > recommend us to use? Any experience or guidance would be great.. > > Thanks, > Mohit. > 1/9/2010 | 3:59 PM. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
