I experienced lots of problems with my store, too. 256MB may be a bit small for your store -- I'm not sure how big yours is. Mine has over 200k parts and only 11k active ones (but that is increasing). I installed Django Debug Toolbar and it said something like 400 queries to bring up the product list in Admin. And that is excessive to me. So, yes, improvements in Satchmo could be made
I'm running on a 768MB Slicehost, though I could probably run it on a 512MB now that I got some tuning done. But our store is only going to add more products, so we are leaving it for now. These are things that I did: * I started with MySQL with MyISAM. It was horrible when I got more than 100 items. I chose PostgreSQL and things got a lot better. Maybe MySQL is InnoDB will be fine as well. * Index your database. Make sure you have a index on slug (I don't think Satchmo/Django does this for you) and see what other items you query by. Slug is big one. Make sure you run analyze after you do this to make sure that the database sees your indexes. * Tune your database. I found this page on PostgreSQL most valuable: http://www.postgresql.org/docs/8.1/static/kernel-resources.html * Caching. If I stop memcache, the site slowly goes to a crawl. Not sure if you have room on a 256MB slice will do it. I did play around with Filesystem caching and that worked well too, though not as good as memcache: https://docs.djangoproject.com/en/1.2/topics/cache/#filesystem-caching * If you have a custom app in front (like I do), be careful to always give Satchmo objects something to work with. I got burned when using forms.MultipleProductForm and not giving it an optional product list. If you don't, then Satchmo will run through all the products until it finds the ones that wants. For me, that was 212k products!! I ended up giving it a QuerySet of Products and that made things worlds better. Adding to the cart became seconds instead of minutes. See if those things help. Mike On Thu, Jul 28, 2011 at 9:11 AM, Bobby Roberts <[email protected]> wrote: > satchmo has become a bloated manatee of a codebase. Does anyone know > why it run so slowly now? Or, do you have to feed it treats or > something secretive to get it running properly? I've got two satchmo > sites on a 256mb slice at slicehost and they are pretty much unusable > at the moment. > > -- > 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. > > -- Mike Hostetler SquarePeg Systems http://www.squarepegsystems.com -- 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.
