| dduvall | |
| Mar 3 2016, 8:33 PM |
| F3523182: transaction profile 1.png | |
| Mar 4 2016, 11:11 PM |
| F3523181: transction profile 2.png | |
| Mar 4 2016, 11:11 PM |
| F3523155: database profile 1.png | |
| Mar 4 2016, 11:08 PM |
| F3523154: database profile 3.png | |
| Mar 4 2016, 11:08 PM |
| F3523156: database profile 2.png | |
| Mar 4 2016, 11:08 PM |
(see T127390: Meet with Security and Ops about a long-term productionization plan for background)
To better accommodate the dashboard database under in Labs, we'll need to know a little more about its traffic profile.
@Ragesoss, would it be possible to get some aggregates from your production logs to get a better sense of controller#action hits and so forth? I've used request-log-analyzer in the past but I've no idea if that's a viable option anymore.
Here's some database profiling from Wiki Ed production for 24 hours. The lion's share of the transactions are probably part of the data update process (which gets more intense as the number of students in active courses, and their number of revisions and articles, grows), rather than being driven directly by website users.
