Caching Options

[James]

Right now, I'm loading up some data VIA the orm. The nature of the data is fairly complex, somewhere around 10-12 tables are touched per insert and about twice that number referencing static helper tables.

For production and day to day use, I've been using django-cache-machine, but I've also been considering Johnny-caching.

For this problem though, johnny won't work because the cache would effectively never get hit.

As far as Django-Cache-Machine, I don't think it's caching .get type queries. I believe it only caches querysets, and then only when you actually iterate over them.

Considering most of my references are .get type queries for this operation, I would think that caching those type of queries would be useful for me during this process.

Now, I won't have to go through this that often, maybe once ever four months, but still I think caching some of the queries up front could speed this up.

What are peoples thoughts on this?

[Phang Mulianto]

Hi i also use johhny cache, why it not hit your cache? Johny cache will cache your queryset and update it when the database table for the queryset updated.

I only cache the queryset without add code in the views,  johny cache handle the rest

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/pvdY4dz4LdgJ.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.