65👍
Didn’t work with Django yet, but here’s my default approach for checking if some component actually writes to redis during development:
First, I flush all keys stored in redis in order to remove old cache entries (never do this in production as this removes all data from redis):
> redis-cli FLUSHALL
Then activate caching in my application, and see what redis does:
> redis-cli MONITOR
You should enter an interactive session where you see every command sent to redis.
Reload your page and on your terminal you should see some SET* operations storing the cache data.
Reload again and if your cache works, you should see some GET* operations retrieving the cached data.
Note: with this method you can check if your cache is actually used. What you can’t see is if your cache helps speeding up your application. For that you have to do performance tests as suggested in the comments.
10👍
You could install the django-debug-toolbar and see if the number of queries decreases when you enable caching. Though I don’t think this is the best solution to the posed question, I still think you want to do this, as you can easily pinpoint costly queries using this setup, and then add the appropriate caching to them.
2👍
Usage of Redis has been focused on lowering the overall query load to the database.
This system likes to work independetly without any coflict 😉
I suggest don’t worry about its operation and don’t change its configs if you can see its activities at:
> redis-cli MONITOR
And there is some elements about your code.
- Django's get_current_language always returns "en"
- Paypal monthly subscription plan settings for first day of the month and making monthly recurring payment – django python