[18:37:50] Krinkle: I'm running out of places to look, do we have metrics for getting save time for a specific wiki? It seems promotheues doesn't append wiki to the metrics by default and there is nothing per wiki in graphite. I'm looking at webrequest at this point but almost all POSTs to action=submit don't end up as edits [19:19:48] Amir1: backend save timing, no we don't purposely fragment that by wiki. We do slice it by content model, user type, and entry point. Which gets you eg wikidata/commons by proxy. And Wikipedia by approximation of volume. [19:20:13] Frontend save timing isn't very representative anymore given VE and such. [19:20:57] Frontend save timing is sliced by wiki almost: https://gerrit.wikimedia.org/g/performance/navtiming/+/2e17c67003f9ed01c39ee5b8db7902fb01f22f07/navtiming/__init__.py#174 [19:21:10] A handful of wikis are picked there [19:22:33] Why would mos action=submit not save edits? Is that action in query param or post data? Are people previewing more often than saving? [19:23:15] Note that with stashing, the actual time is split between two requests with the main one merely polling memcached. [19:23:52] What's the higher even question? [19:23:58] higher level* [21:06:50] I need it for ptwiki which is not there :( [21:07:16] yeah, most of things I get there don't correlate to any edits on the wiki :( [21:09:26] action=submit includes previews and diffs, I think? [21:10:11] https://www.mediawiki.org/wiki/Manual:Parameters_to_index.php#submit [21:10:35] I don't know about diff but preview I'm sure [21:10:35] and CSRF errors and whatnot [21:10:42] I'm counting POSTs [21:11:52] you should probably check for wpSave (button name for the save button) [21:21:16] ah, thanks