Change Details

As we add more clauses to the queries, they're going to take longer. Before we launch category tracking in production, we should look into how much slower our queries get with it. Let's add logging to see how long "Update stats" takes every time someone updates stats for an event. That's the time taken to run all individual queries on each wiki included in the event. It would be fantastic if we can surface those stats in the UI on the **staging** instance. If not, it is okay to have them in the logs.

As we add more clauses to the queries, they're going to take longer. Before we launch category tracking in production, we should look into how much slower our queries get with it. Let's add logging to see how long "Update stats" takes every time someone updates stats for an event. That's the time taken to run all individual queries on each wiki included in the event. It would be fantastic if we can surface those stats in the UI on the **staging** instance. If not, it is okay to have them in the logs. Create tasks to complete the discovered work.

As we add more clauses to the queries, they're going to take longer. Before we launch category tracking in production, we should look into how much slower our queries get with it. Let's add logging to see how long "Update stats" takes every time someone updates stats for an event. That's the time taken to run all individual queries on each wiki included in the event. It would be fantastic if we can surface those stats in the UI on the **staging** instance. If not, it is okay to have them in the logs. Create tasks to complete the discovered work.