Am 03.11.2011 18:42, schrieb Tom Evans: > On Thu, Nov 3, 2011 at 2:22 PM, Thomas Guettler <h...@tbz-pariv.de> wrote: >> Hi, >> >> I try to reduce the number of db-queries in my app. >> >> There is a model which changes almost never. It is like a "type of ticket" >> in a trouble ticket system. >> >> On one page there are seven SQL-Queries (SELECT .... FROM ticket_type where >> id=123) which of course always return >> the same result. >> >> I want to cache the objects: >> >> t1=TicketType.objects.get(id=123) >> t2=TicketType.objects.get(id=123)
> Hey > > I wouldn't use this approach - caching in threadlocals is the wrong > place to cache. Primarily, this is because the cache is in the wrong > location - it is per thread, which means you must have n caches for n > threads. This is an inefficient use of memory, it would be better to > cache at a different level, eg memcached, redis, etc. Hey, The database queries (without cache) are fast enough. There are just too many. Sometimes up to ten equal SELECT by primary key statements during one request. If you substitute fast sql queries with fast cache access, I don't have a benefit. > Secondly, this caching is very naïve. Queries are never evicted from > the cache, ... Yes, I know. The lines I wrote were just a prototype. I want to use this for things that doesn't change for several days. The cache could get purged by touching the wsgi-file, which reloads the wsgi worker processes. Thomas -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
