On Mon, Sep 29, 2014 at 3:10 PM, Dario Taraborelli <dtaraborelli@wikimedia.org> wrote:On Sep 27, 2014, at 11:42 AM, Aaron Halfaker <ahalfaker@wikimedia.org> wrote:I'm not surprised that PageContentSaveComplete is big. That's a very useful table and it sees a lot of rows for good reason (every revision saved on every wiki).As for the Multimedia/Mediaviewer tables, we should probably ping someone on that team to discuss them.Dario, can you speak for the MobileWebClickTracking and MobileWikiAppToCInteraction schemas?The mobile web team uses the MobileWebClickTracking to get a rough heatmap of taps on prominent UI elements, and the apps team uses MobileWikiAppToCInteraction to measure engagement with the table of contents on the Wikipedia app. They're both not primary metrics we're tracking but are useful to check in on every once in awhile. Does that answer your question?neither I nor Oliver are using this data but it’s used for some Limn dashboards by the Mobile team. Copying Maryana and Kaldari so they can chime inDOn Sat, Sep 27, 2014 at 2:02 PM, Sean Pringle <springle@wikimedia.org> wrote:_______________________________________________Hi :-)These are the largest Eventlogging tables on m2-master:
145G MobileWebClickTracking_5929948.ibd
94G PageContentSaveComplete_5588433.ibd
61G MediaViewer_8572637.ibd
57G MediaViewer_8245578.ibd
30G MultimediaViewerNetworkPerformance_7917896.ibd
29G MediaViewer_8935662.ibd
24G MobileWikiAppToCInteraction_8461467.ibd
Are these sizes roughly expected?Anything we can discard or reduce?
Where did the discussion on purging data end up?
No immediate problems here, just rattling cages :-)BR/s
--DBA @ WMF
_______________________________________________
Analytics mailing list
Analytics@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list
Analytics@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics--