There is over six months of data in MobileWebClickTracking_5929948.
Maryana, maybe the older data could be purged as well? That'd probably
speed up the queries.

Dan

On 22 December 2014 at 09:29, Maryana Pinchuk <[email protected]>
wrote:

> Thanks for the heads up -- the MobileWebDiffClickTracking schema has
> gotten way too big to query, it looks like. We'll figure out a way to break
> it up into more manageable chunks so it doesn't cause issues like this.
>
>
>
> On Dec 22, 2014, at 7:57 AM, Nuria Ruiz <[email protected]> wrote:
>
> Adding mobile tech so they are aware, I am guessing we need to query for
> that data in a more efficient fashion.
>
>
>
> On Mon, Dec 22, 2014 at 4:10 AM, Sean Pringle <[email protected]>
> wrote:
>
>> Had to kill queries, lest analytics-store grind to a halt and take even
>> longer to recover.
>>
>> These ones: https://gerrit.wikimedia.org/r/#/c/178381/
>>
>> On Sun, Dec 21, 2014 at 8:09 PM, Sean Pringle <[email protected]>
>> wrote:
>>>
>>> This last few days analytics-store replication has started to lag by
>>> some hours. Currently s1 (enwiki) and s5 (dewiki, wikidatawiki) are most
>>> affected. Eventlogging is not lagging, due to the nicely batched writes it
>>> does now-a-days :-)
>>>
>>> There are many slow queries running from the research user on stat1003,
>>> referencing eventlogging tables like MobileWebDiffClickTracking*.
>>>
>>> I'm not sure who belongs to them, or if they're new, or if they're safe
>>> to kill, so this is mainly a heads-up email. Let us know if ops should kill
>>> stuff to let the box catch up again.
>>>
>>> BR
>>> Sean
>>> --
>>> DBA @ WMF
>>>
>>
>>
>> --
>> DBA @ WMF
>>
>> _______________________________________________
>> Analytics mailing list
>> [email protected]
>> https://lists.wikimedia.org/mailman/listinfo/analytics
>>
>>
>


-- 
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation
_______________________________________________
Analytics mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/analytics

Reply via email to