Improving Performance of Tags about acts-as-taggable-on

[bradeaton]

Just pinging on this question again... My main question is about tags on existing records. Our application is multi-tenant in the same DB. There is an accounts table and a contacts table. The contacts table has an account_id column. If I add acts_as_taggable_tenant :account_id to the contact model, will all the tags on existing contacts records benefit from this or would I have to delete the tags from each contact and add them back?

[NurfitraPujo]

Hello @bradeaton i know this is old post but anyway, our team also use this gem for tagging conversation rooms in our application. There is one heavy query that do aggregates on our model (rooms count by tag). This query can process up to 8 millions row at once so itu is very slow before optimi zed (~30s) and now it becomes ~5s.

My comments on your query is:

1. Just select the necessary columns
2. Make sure to create multicolumn index that consisted of all columns used in your where clause. include columns that used in your select and join keys

[darkamenosa]

I faced the almost same problem. It seems the best way is to create a new column on the table and store the cached tag. And query on that table not using these tables. (Ref: https://github.com/mbleigh/acts-as-taggable-on/wiki/Caching

I'm testing with my local, hope this works.

[sumirolabs]

Another solution is to add a new scope that reproduces the original query, eg

scope :with_tag, lambda {|tag| joins(:taggings).where(taggings: { tag_id: tag.id }) }

and then replace the tagged_with calls with this scope.

It would be nice to add the option of passing in an actual tag (instead of the name) and then use the query in the scope above.