Out of curiosity, why do you care about the amount of RAM available on a dyno?
I generally run either delayed job workers or web processes on Heroku's dyno grid; I don't have any general-purpose compute loads that require gigabytes of RAM yet, but if I did, I'd probably look for either a hosting provider that specialized in running the type of process that needs so much memory (e.g. a database), or start thinking about buying compute power lower down the stack (EC2/colo). Maybe your needs are different than mine, though? On Fri, Nov 25, 2011 at 11:16 AM, anentropic <[email protected]> wrote: > I have some (Django) sites on an 80MB WebFaction hosting account. > > I see that a single dyno on Heroku gets 512MB... for free! (albeit > I'll pay for db and S3 storage etc...) > > The WebFaction pricing pages says: > "This is the actual memory available to your long-running processes > (for instance, your Rails or Django processes). Unlike in a VPS, the > memory used by the operating system, the main web server and the > database servers doesn't count towards your memory usage" > > In the WF process list I see Apache httpd workers for my Django/wsgi > app. > > Is this broadly comparable to Heroku... i.e. the whole 512MB is > available to user processes? > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" 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/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
