Unmaintained Trending Content Tags 1.1.8

• Persistent tag counts from redis to mysql should better than race conditions if the persistence is triggered at the same time. Previously 1 attempt would just die, now it will silently stop rather than cause errors.

• Correctly purge a tag's trending information when a tag is deleted
• Fix add-on compatibility with add-ons which hook tags being deleted
  • Recommend updating if you use Tag Essentials
• Add warning that counting guest usage causes increased write load to the redis backend.

• Improve reliability of installer to create tables if reinstalling

• Improve old trending tag summarization so it correctly breaks up it's workload across multiple background deferred requests.
  • Additionally, this prevents a case where it would continuously loop failing to prune rows due to a logic error. This error previously wasn't observable, as it would do most of the work in the one request due to a bug where the limit on the rows to check was being ignored.

• Correctly limit the number of tags being summarized to the configured amount, and push the rest into a deferred task.
  • Recommend changing "Summarize Sample Limit" to a much lower value than the previous default. New value is 100 tags, not 10000.

• When the trending sidebar is disabled, don't display an empty trending sidebar entry.

• Prevent error on a new install.

• Reduce locking on MySQL fallback path.
• Prevent potential "ERR no such key" error.

If using Zend Redis Cache, version 1.1.14 is required.

• Automatically use Redis to cache per-page requests until they are need to be compiled to show trending content tags.
  • Replaces potentially expensive insert-select-update query with a few simple Redis inserts, tag usage counters are then destaged later and not on each page hit.
  • Once the sample collection window is closed, or the trending cloud cache expires, tag counters are then persisted to the database.
• Still contains MySQL based fallback if Redis is not available.

Implement summarization of old tags via daily cron.

• By a minimum time (after 72 hours by default), samples are summarized into smaller blocks (6 hour sample window).

Warning: initial summarization of older tags can take some time.