3👍
Whilst I can’t say for certain, I’ll add this as an answer anyway to be judged on it…
As you know, django’s default cache is the LocMemCache
Which in the above docs you’ll find:
Note that each process will have its own private cache instance
And I think this is all you’re seeing. The jump in memory is just the storage of your query. I’d think you only need to be concerned if this memory usage continued to grow beyond a normalcy.
The same doc also says it might not be very viable in production so it might be time to move beyond this, which would also allow you to see if caching was the culprit.
Source:stackexchange.com