Suor/django-cacheops

A slick ORM cache with automatic granular event-driven invalidation.

Chetan Dhembre

@chetandhembre

it is not also possible my function gets start and end from another function .. i guess cacheops wont help me with my unique usecase

atleast function level cache

will use from cacheops import cache in this case

Alexander Schepanovski

@Suor

You can use custom key func here

Chetan Dhembre

@chetandhembre

like?

does cacheops provide this feature? it is in TODOS

Alexander Schepanovski

@Suor

def _key_func(func, args, kwargs, extra=None):
    start, end = args
    # ...
    return key

@cached_as(timeout=30 * 60, key_func=_key_func)
def _get_a(start, end):
    a = some_function_call(start, end)
    # Do not cache empty results
    if not a:
        raise UncachedResult(a)

    return a

Chetan Dhembre

@chetandhembre

this is great ..

Alexander Schepanovski

@Suor

I feel that you are overcomplicating though.

Chetan Dhembre

@chetandhembre

why i havent read it before

Alexander Schepanovski

@Suor

Because it's not documented

Chetan Dhembre

@chetandhembre

Chetan Dhembre

@chetandhembre

btw thanks for cacheops

Alexander Schepanovski

@Suor

you are welcome

Chetan Dhembre

@chetandhembre

it just work.. like nginx and redis respect

Alexander Schepanovski

@Suor

Thanks

Harish Sundararaj

@harishzen

Hi. I'm wondering if there is any documentation out there comparing this with johnny cache?

Alexander Schepanovski

@Suor

Johnny-cache is not supported anymore, it's working analog is django-cachalot. The main difference between cacheops and both of them is that they invalidate entire table every time any changes to it is made whereas cacheops is granular.

Chetan Dhembre

@chetandhembre

can i use cacheops without django?

as our django app using cacheops do not want to use different lib for caching

Alexander Schepanovski

@Suor

The smart part of cacheops caches django ORM querysets and other things basing on that, so I can't see how it could be used without django.

Simple and file cache might be used separately, you'll still need django as dependency and to configure them

Not sure what's the issue with the app

Chetan Dhembre

@chetandhembre

I want to use simple cache.. but at start of cacheops it expect to read config from settings file

Chetan Dhembre

@chetandhembre

got it

Chetan Dhembre

@chetandhembre

i guess still i have some issue

from cacheops.simple import RedisCache

I am importing this

Alexander Schepanovski

@Suor

You can configure django with django.conf.settings.configure()

codegeschrei

@codegeschrei

Hey there! I just wanted to ask why caching in admin is turned off?

Alexander Schepanovski

@Suor

To be extra safe. And more for historical reasons, there were lots of limitations in invalidating m2m for example.

Another reason - caching for admin doesn't make sense anyway: low traffic, high updates, different queries than in the app. Useless bloat.

codegeschrei

@codegeschrei

Thanks for your fast response, too bad though, for my project it'd be a really good thing.

Alexander Schepanovski

@Suor

You can overwrite ModelAdmin.get_queryset()

Marcio Ribeiro

@b1n_twitter

How hard would it be to make cacheops work with Django 1.6?

Alexander Schepanovski

@Suor

You can just use cacheops 2.4.3

Marcio Ribeiro

@b1n_twitter

Will check it out, thanks

Shashank Parekh

@sp1rs

Small Issue.
Let say 2 things are running parallelly, first to get the object which is cached and second the object which is saving that object (That is invalidating the cache). So is it possible that before the get operation, the cache get invalidated and we get the wrong or nothing from the 1st operation?

Matthew Egan

@mattjegan

Hey, would anyone be able to answer this cacheops question? https://stackoverflow.com/questions/44821010/connecting-django-signal-handlers-in-tests

Alexander Schepanovski

@Suor

It's impossible to say anything without test code. Signal setup looks fine, you may just not using cacheops in your test code.

Sam Buckingham

@BuckinghamIO

Does cache ops potentially have issues with prefetch_related?

Alexander Schepanovski

@Suor

Abhishek Menon

@mav-erick

Hey guys. Amazing project! @Suor can i cache serializers if i am using DRF using cache ops?

Abhishek Menon

@mav-erick

I am running a multitenant application using Postgres schemas. The schema varies depending on the tenant. Will it cause problems when using this package?

Alexander Schepanovski

@Suor

@mav-erick as long as there are querysets inside it should work. Many people use cacheops with DRF just fine.

If you have the same SQL for different queries you will need to use cache prefix, see https://github.com/Suor/django-cacheops#sharing-redis-instance

Abhishek Menon

@mav-erick

Hi @Suor. Thanks for the info. One final question. Will the cache be invalidated with there are changes in a related model(Foreign keys and stuff) ?

Alexander Schepanovski

@Suor

Will be invalidated for any joined models via conditions. Won't be invalidated if .select_related() object changes. .prefetch_related() creates a separate query for related which is invalidated separately, so you might want to use that if the thing with .select_related() is an issue. See all CAVEATS here https://github.com/Suor/django-cacheops#caveats

Abhishek Menon

@mav-erick

Perfect. Thanks a lot!

Nikita Vilunov

@vilunov

Hiya all! Is it possible to keep the cache of an arbitrary function hot on time invalidation? I am caching some functions and a view. Currently I'm thinking about introducing a periodic celery task which invalidates that cache and fetches the view, but maybe there is a cleaner solution

Alexander Schepanovski

@Suor

Running a function after invalidation possibly via celery .delay() is the way to go. There is no any built in way to do that and there is no way to introspect what function results were just invalidated.

Where communities thrive

People

Repo info

Activity