Comments on: Improving Django Cache – Part III http://richwklein.com/2009/08/11/improving-django-cache-part-iii/ A blog about nothing Tue, 06 Apr 2010 16:48:33 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Rich http://richwklein.com/2009/08/11/improving-django-cache-part-iii/comment-page-1/#comment-10596 Rich Thu, 13 Aug 2009 21:06:19 +0000 http://richwklein.com/?p=670#comment-10596 You are beating me to the punch. My next post in the series is on creating a cache decorator. :) You are beating me to the punch. My next post in the series is on creating a cache decorator. :)

]]> By: Rich http://richwklein.com/2009/08/11/improving-django-cache-part-iii/comment-page-1/#comment-11905 Rich Thu, 13 Aug 2009 21:06:00 +0000 http://richwklein.com/?p=670#comment-11905 You are beating me to the punch. My next post in the series is on creating a cache decorator. :) You are beating me to the punch. My next post in the series is on creating a cache decorator. :)

]]> By: Ben Bangert http://richwklein.com/2009/08/11/improving-django-cache-part-iii/comment-page-1/#comment-10595 Ben Bangert Thu, 13 Aug 2009 20:20:08 +0000 http://richwklein.com/?p=670#comment-10595 And here's that code snippet with formatting: http://pylonshq.com/pasties/abfff860550a3cb508d5dd817d502070 And here’s that code snippet with formatting:
http://pylonshq.com/pasties/abfff860550a3cb508d5dd817d502070

]]> By: Ben Bangert http://richwklein.com/2009/08/11/improving-django-cache-part-iii/comment-page-1/#comment-11904 Ben Bangert Thu, 13 Aug 2009 20:20:00 +0000 http://richwklein.com/?p=670#comment-11904 And here's that code snippet with formatting: http://pylonshq.com/pasties/abfff860550a3cb508d5dd817d502070 And here’s that code snippet with formatting:
http://pylonshq.com/pasties/abfff860550a3cb508d5dd817d502070

]]> By: Ben Bangert http://richwklein.com/2009/08/11/improving-django-cache-part-iii/comment-page-1/#comment-10594 Ben Bangert Thu, 13 Aug 2009 20:18:58 +0000 http://richwklein.com/?p=670#comment-10594 Hmm, not sure it'd be ideal to put in there. What would probably work best is to make a Django middleware, that add's a cache instance to the request object. That way inside a Django function, you could do something like: def myview(request): @request.cache.cache('my_search_func', expire=3600) def get_results(search_param): # do something to retrieve data data = get_data(search_param) return data results = get_results('demo') return Response(results) This way you could use the nice decorator API: http://beaker.groovie.org/caching.html#decorator-api You'd also hopefully be able to pass the appropriate beaker configuration options to the middleware then as well, since Beaker supports several different back-ends (even simultaneously), so that you could change which backend is used on a per-cache basis as appropriate. Hmm, not sure it’d be ideal to put in there. What would probably work best is to make a Django middleware, that add’s a cache instance to the request object.

That way inside a Django function, you could do something like:

def myview(request):
@request.cache.cache(‘my_search_func’, expire=3600)
def get_results(search_param):
# do something to retrieve data
data = get_data(search_param)
return data
results = get_results(‘demo’)
return Response(results)

This way you could use the nice decorator API:
http://beaker.groovie.org/caching.html#decorator-api

You’d also hopefully be able to pass the appropriate beaker configuration options to the middleware then as well, since Beaker supports several different back-ends (even simultaneously), so that you could change which backend is used on a per-cache basis as appropriate.

]]> By: Ben Bangert http://richwklein.com/2009/08/11/improving-django-cache-part-iii/comment-page-1/#comment-11903 Ben Bangert Thu, 13 Aug 2009 20:18:00 +0000 http://richwklein.com/?p=670#comment-11903 Hmm, not sure it'd be ideal to put in there. What would probably work best is to make a Django middleware, that add's a cache instance to the request object. That way inside a Django function, you could do something like: def myview(request): @request.cache.cache('my_search_func', expire=3600) def get_results(search_param): # do something to retrieve data data = get_data(search_param) return data results = get_results('demo') return Response(results) This way you could use the nice decorator API: http://beaker.groovie.org/caching.html#decorator-api You'd also hopefully be able to pass the appropriate beaker configuration options to the middleware then as well, since Beaker supports several different back-ends (even simultaneously), so that you could change which backend is used on a per-cache basis as appropriate. Hmm, not sure it’d be ideal to put in there. What would probably work best is to make a Django middleware, that add’s a cache instance to the request object.

That way inside a Django function, you could do something like:

def myview(request):
@request.cache.cache(‘my_search_func’, expire=3600)
def get_results(search_param):
# do something to retrieve data
data = get_data(search_param)
return data
results = get_results(‘demo’)
return Response(results)

This way you could use the nice decorator API:
http://beaker.groovie.org/caching.html#decorator-api

You’d also hopefully be able to pass the appropriate beaker configuration options to the middleware then as well, since Beaker supports several different back-ends (even simultaneously), so that you could change which backend is used on a per-cache basis as appropriate.

]]> By: Rich http://richwklein.com/2009/08/11/improving-django-cache-part-iii/comment-page-1/#comment-10591 Rich Thu, 13 Aug 2009 18:46:32 +0000 http://richwklein.com/?p=670#comment-10591 I'm just taking a looking at your source code. Pretty nice, it would be interesting if you could add a wrapper so it could be used as a custom Django cache backend. http://docs.djangoproject.com/en/dev/topics/cache/ I’m just taking a looking at your source code. Pretty nice, it would be interesting if you could add a wrapper so it could be used as a custom Django cache backend.

http://docs.djangoproject.com/en/dev/topics/cache/

]]> By: Rich http://richwklein.com/2009/08/11/improving-django-cache-part-iii/comment-page-1/#comment-11902 Rich Thu, 13 Aug 2009 18:46:00 +0000 http://richwklein.com/?p=670#comment-11902 I'm just taking a looking at your source code. Pretty nice, it would be interesting if you could add a wrapper so it could be used as a custom Django cache backend. http://docs.djangoproject.com/en/dev/topics/cache/ I’m just taking a looking at your source code. Pretty nice, it would be interesting if you could add a wrapper so it could be used as a custom Django cache backend.

http://docs.djangoproject.com/en/dev/topics/cache/

]]> By: Ben Bangert http://richwklein.com/2009/08/11/improving-django-cache-part-iii/comment-page-1/#comment-10590 Ben Bangert Thu, 13 Aug 2009 18:31:16 +0000 http://richwklein.com/?p=670#comment-10590 Or you could just setup and use Beaker's caching system in Django: http://beaker.groovie.org/ Fast, performs great, oh, and it actually prevents the dog-pile effect which kills most of the hodge-podge caching stuff. It also handles the messy locking to prevent multiple processes on the same machine from all re-creating the cached value at once, and its been used in large production systems for quite a long while now. I'd be happy to include some stuff to make it easier to use from Django if someone cares to submit some patches. :) Or you could just setup and use Beaker’s caching system in Django:
http://beaker.groovie.org/

Fast, performs great, oh, and it actually prevents the dog-pile effect which kills most of the hodge-podge caching stuff. It also handles the messy locking to prevent multiple processes on the same machine from all re-creating the cached value at once, and its been used in large production systems for quite a long while now.

I’d be happy to include some stuff to make it easier to use from Django if someone cares to submit some patches. :)

]]> By: Ben Bangert http://richwklein.com/2009/08/11/improving-django-cache-part-iii/comment-page-1/#comment-11901 Ben Bangert Thu, 13 Aug 2009 18:31:00 +0000 http://richwklein.com/?p=670#comment-11901 Or you could just setup and use Beaker's caching system in Django: http://beaker.groovie.org/ Fast, performs great, oh, and it actually prevents the dog-pile effect which kills most of the hodge-podge caching stuff. It also handles the messy locking to prevent multiple processes on the same machine from all re-creating the cached value at once, and its been used in large production systems for quite a long while now. I'd be happy to include some stuff to make it easier to use from Django if someone cares to submit some patches. :) Or you could just setup and use Beaker’s caching system in Django:
http://beaker.groovie.org/

Fast, performs great, oh, and it actually prevents the dog-pile effect which kills most of the hodge-podge caching stuff. It also handles the messy locking to prevent multiple processes on the same machine from all re-creating the cached value at once, and its been used in large production systems for quite a long while now.

I’d be happy to include some stuff to make it easier to use from Django if someone cares to submit some patches. :)

]]>