Looking at the Web Views and Agg Views (in the .Text admin screen), I just realized a statistics bottleneck in .Text's database schema, and I wanted to write about it. I see the same problem a lot, and I see many developers fall into the bottleneck of row-level locking at the database on those records that need the statistical counting/summation/average/whatever.
Basically, you insert all the statistical “hits“ into a raw table, (I usually call it ActivityList, linked to the record via an ActivityListId), and have a process that collects and summarizes the data at a frequency that minimizes this contention.
I'll update this post once the article is finished with the link: [insert link here]