Satchmo is a pretty large codebase, with lots of dependencies, so it
is definitely possible that it will take up a lot of ram. That said,
your deployment method can have a lot to do with how much ram you are
using. You mention httpd, so I'm guessing you are using CentOS or
RHEL, with apache and probably mod_python. Is that the case? There are
much better options for ram usage than that.

So, what is your current deployment setup?

Alex

On Thu, Nov 11, 2010 at 1:30 PM, Josh <[email protected]> wrote:
> I have been working on a satchmo site with ~3000 products that has
> repeatedly over the past week or so crashed the server it is running.
> It is on a VPS with 2G dedicated ram.  It seems that once the httpd
> process allocates memory it never releases it, eventually taking all
> available memory and crashing the server.  I tried opening about ten
> pages from the site and repeatedly hard refreshed them and watched the
> memory usage (via top) shoot up more than 150m in about 10 minutes,
> its still going up as I write this.
>
> Are there any known memory leaks in satchmo?  Why would memory usage
> continue to go up after I have stopped hard refreshing?  (I guess it
> is possible that other people are visiting the site but every two
> second or so it seems to go up about 1m, which if it continues the
> server will crash again).  Thanks in advance for any help.
>
> -Josh
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Satchmo users" 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/satchmo-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Satchmo users" 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/satchmo-users?hl=en.

Reply via email to