Similar setup to yours. Initialize Django with multiple caches then test the performance of get/set/delete operations. Script in Github repo at tests/benchmark_djangocache.py Results are here: http://www.grantjenks.com/docs/diskcache/djangocache-benchmarks.html I'm measuring multiple percentiles: 50th (median), 90th, 99th, and max.
I'm not sure what "multiple web heads" refers to but I will guess you mean a load balancer with multiple servers behind it. That is a scenario where you've probably outgrown DiskCache. Although if you load balance consistently (say by ip-hash) then the issue can be mitigated.
Comment
Similar setup to yours. Initialize Django with multiple caches then test the performance of get/set/delete operations. Script in Github repo at tests/benchmark_djangocache.py Results are here: http://www.grantjenks.com/docs/diskcache/djangocache-benchmarks.html I'm measuring multiple percentiles: 50th (median), 90th, 99th, and max.
I'm not sure what "multiple web heads" refers to but I will guess you mean a load balancer with multiple servers behind it. That is a scenario where you've probably outgrown DiskCache. Although if you load balance consistently (say by ip-hash) then the issue can be mitigated.