Kind regards,
Hannus
You would need to ask them whether they support it; they're the ones
who would know.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
I personally use webfaction for public hosting, but its a major pain
Just buy your own box
Justin
...or go the VPS route. Any hosting company offering Xen-based virtual
servers (I used provps.com, who have been great) can give you the
flexibility of your own server without the cost of a dedicated server.
I have a site on webfaction - 40MB. After much tweaking I got each
django instance down to 15 mb and things were ok. Today I got a
notice saying I am using 105 mb - look at the stats and find that
each instance is using 35 MB. I have made no change. The rest of my
apps are on my own vps, so no problem. But how did 15mb become 35mb
over time?
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
Justin
Maybe you need to decrease your ServerLimit? Each forked server process leads
to increased memory usage. For a really low volume site, you can get away with
ServerLimit 1, although I'd be sure to host your media files in a different
instance (webfaction has docs for doing this somewhere).
Make sure that Django and Python debug settings are disabled, too (apache2.conf
PythonDebug, settings.py DEBUG).
-Forest
--
Forest Bond
http://www.alittletooquiet.net
> I have the same problem. They sent me the same notice with a couple
> links to their forums with suggestions as how to keep your memory
> (RSS) down, like regular restarts of apache and setting DEBUG = False
> in the settings. Follow these tips and your memory usage should be
> within acceptable limits.
their memory test is at a specific point of time on a monday. I have
followed all the tips and brought the memory down - now it is shot
up, I think there is a memory leak on their side. Best thing would be
to shut down the site every monday ;-)
> Maybe you need to decrease your ServerLimit? Each forked server
> process leads
> to increased memory usage. For a really low volume site, you can
> get away with
> ServerLimit 1, although I'd be sure to host your media files in a
> different
> instance (webfaction has docs for doing this somewhere).
did that
>
> Make sure that Django and Python debug settings are disabled, too
> (apache2.conf
> PythonDebug, settings.py DEBUG).
did all this - I am still getting around 35 MB per instance. And it
is not the fault of webfaction. The same site on my local machine
gives the same figure. This on the latest svn in both cases. The last
time I looked at these figures, it was around 12-15mb an instance.
Any other clues?
when I asked them to install python Imaging library - they refused.
Told me that their policy is not to install extra libraries, but you
should be able to do that in your user space.
Evgeny.
--
耑此佈達
東涼
I remember someone there saying that right after you restart Apache
the RAM usage is low, but after it's served a few requests the usage
jumps, and then stays high -- ie, it's normal. Had you kept it at
12-15 for a long time previously? Is it possible that the last time
you checked usage was just following an Apache restart?
Otherwise, my solution to these problems is to host unpopular websites
that no one looks at.
Yrs,
E
> when I asked them to install python Imaging library - they refused.
> Told me that their policy is not to install extra libraries
a service that claims to support python and considers PIL an
(irrelevant) 'extra' library should be avoided like plague
This is probably normal memory usage. This is not a problem, as long as it
doesn't grow much beyond that, right?
I have two small sites that share a lot of code running on a webfaction account.
With ServerLimit 1 and media hosted on the main apache instance (which doesn't
count against me for RAM usage), I stay pretty constant at 32-35MB. I don't
think it would be possible to get much lower than that. Libraries have to get
loaded somewhere, afterall.
I guess maybe you could try to reduce your imports.
> I guess maybe you could try to reduce your imports.
heavy use of PIL and reportlab is there even though there are at the
most three users at a time. I remember running 4 sites on pre .91
django on zettai and keeping well within the 64 mb limit. Sigh.