On Wed, Sep 16, 2009 at 12:21 PM, Douglas Sims <ratsb...@gmail.com> wrote:
> I'm curious... what is the hardware like on the one server? How many CPUs > and RAM? > > AMD Athlon quad core, running 32 bit Ubuntu Hardy. 16 GB of RAM. Algebra.Com data is stored on an SSD> > Also, a few thoughts... > > - You do a 301 from algebra.com to www.algebra.com. That doesn't take > much work from the server, but why not just serve up everything from the > original location? > > then I will have to serve algebra.com twice to all search engines. > - The algebra problem I just tried returned twelve separate images. What > if, instead of serving gifs you displayed each stage of transformation of > the equation using HTML and CSS? That would be rather tricky with things > like root signs but I think it could be done - though a bit of work. > > I rather like the way I do it, I let my site render images exactly how I want, as opposed to letting browsers do it. > I wish this site had been around when I was in high school. > > > thanks. I have some real math addicts on my site, who solved many thousands of problems and helped hundreds of kids. I am glad to serve them. i > > On Wed, Sep 16, 2009 at 11:48 AM, Adam Prime <adam.pr...@utoronto.ca>wrote: > >> Igor Chudov wrote: >> >>> >>> >>> On Wed, Sep 16, 2009 at 11:05 AM, Michael Peters >>> <mpet...@plusthree.com<mailto: >>> mpet...@plusthree.com>> wrote: >>> >>> On 09/16/2009 11:49 AM, Igor Chudov wrote: >>> >>> 1) Use a load balancer like perlbal (I am already doing that) >>> >>> >>> A load balancer is good but so are proxies. If you can separate your >>> application server from the server that servers static content then >>> you'll get a boost even if they are on the same machine. >>> >>> >>> I have very little static content. Even images are generated. My site >>> generates images of math formulae such as (x-1)/(x+1) on the fly., >>> >> >> I can understand generating them on the fly for flexibility reasons, but >> I'd cache them, and serve them statically after that, rather than regenerate >> the images on every single request. You can accomplish that in the app >> itself, or just by throwing a caching proxy in front of it (maybe you're >> already doing this with perlbal) >> >> Adam >> > >
