FeinCMS and DjangoCMS

Spent sometime working with both over the last month, created 2 ecommerce sites around these and here are some observations which may help people decide what works for them FeinCMS was a pain to get started with, i had to base it all on the default example as the documentation was not enough to get it all started from scratch. I was using the trunk as it has goodies [like a blog] which the stable did not have....

May 28, 2010 · 1 min · 188 words · Me

obsessing about bdb, queues

So my nightmares do no cease to end, still debating queue solutions and databases. After spending a lot of time thinking about how to handle 100 million entries , concurrency and a lot of jazz here are some conclusions that I have reached. Tokyo Tyrant needs some testing personally. Can it work well within a constrained VPS ? I doubt that after reading all the test results. So need to do a benchmark for this....

October 9, 2009 · 1 min · 162 words · Me

Nginx + django fcgi lessons

Today was a good day as i learned some valuable lessons about django and nginx. ALWAYS close the database cursor in django, it can lead to some pretty wierd memory issues going forward. FIND the most optimal number of database connections you initialize for you connection pooling. This will let you optimize on memory going forward. ENSURE that you do not set a very high client_timeout, this means that if connections are not explicitly not closed by the client then the web server will not timeout....

January 19, 2009 · 1 min · 138 words · Me

Django : Optimizations within the platform

In my experience with both rails and django, i would have to admit that a lot of things need to be improved at the core of these platforms so that developers can truly deploy a really fast production site. Let talk about what we did at kwippy to make it that much more faster than the default Django setup. Use memcached properly : The trick in getting speed is to cache all logged out pages and heavy caching of the user objects when logged in....

November 18, 2008 · 2 min · 387 words · Me

Django : using a seperate memcached cloud for sessions

When you are using a platform like django you realise how slow sessions can get when you are using the database as a backend. The problem of using a memory cache like memcached is the fact that when you restart the server to refresh the cache or remove stale objects, the problem is that you lose your sessions data and a lot of people using your site get logged out. The only solution to this problem is to use 2 memcached instances , one for your regular python objects and another for your sessions objects … this is not a default feature in Django....

November 18, 2008 · 2 min · 400 words · Me