576106 - [k] Make Tag models memcacheable

Status: RESOLVED WORKSFORME

(support.mozilla.org :: Questions, task)

Description

[Erik Rose [:erik][:erikrose]]

Perhaps use a proxy model. Putting this off till after the Summit in favor of more demo-able stuff.

Comment 1

[Erik Rose [:erik][:erikrose]]

This turns into a serious dive into cache invalidation. Pushing out of 2.2. jsocol says the DB won't catch on fire.

Notes about how to resume implementation are at http://github.com/erikrose/kitsune/blob/576106-memcache-tags/apps/questions/tests/test_models.py#L183. In summary, Cache Machine doesn't yet support invalidation along many-to-many relationships, largely because the traffic to and from memcached can be immense. Also, it doesn't yet support invalidation along GenericForeignKeys (though that's easier to fix).

Comment 2

[Erik Rose [:erik][:erikrose]]

Sticking our flush lists in redis should make the many-to-many invalidation we need much more feasible.

Comment 3

[James Socol [:jsocol, :james]]

Not related to KB => out of 2.3.

Comment 4

[Erik Rose [:erik][:erikrose]]

taggit 0.9 allows for custom Tag models and should thus make this more possible. http://alexgaynor.net/2010/sep/21/django-taggit-09-released/

Comment 5

[Kadir Topal [:atopal]]

P2 leads me to believe that this was considered quite high priority. Does it still make sense to cache these? Or can we close this bug?

Comment 6

[Ricky Rosario [:rrosario, :r1cky]]

Let's hold off until we implement the new IA and then make a call. We may reduce our usage of taggit or kill it altogether. It definitely isn't a P2 at the moment.

Comment 7

[Ricky Rosario [:rrosario, :r1cky]]

We do cache tags. we just dont use cache-machine.