Activity visit count aggregation inefficient #39
Description
The aggregation of activity visits uses the potentially large table logstore_standard_log.
As pointed out in #30 (comment) the aggregation goes through unindexed columns, which is inefficient in search operations.
I see a design flaw in this feature.
One, the obvious one, it relies on the logstore_standard_log table and the mentioned not-indexed columns.
Second, the user is not told the time range the activity visits are from, which implicitly is the value of the setting logstore_standard | loglifetime.
I'm not sure if there are more efficient alternatives to this, if not, then it would be best to drop the feature altogether.