Max Semenik wrote:
> Parser cache is in MySQL, you can't displace anything out of it by
> putting stuff into memcached.
You're wrong here.
Although there's usually plenty of space, so this isn't somehting to be
worried about.
(I would link to a graphic of memcached servers, but I'm unable to find
This appears to have been due to a network link issue. One of the
uplinks from our row A switch in eqiad was spewing out input framing
errors, causing some packets to be dropped.
This link has been taken down for troubleshooting and the issue
appears to be gone. Please let us know ASAP if you st
On 25.03.2012, 2:28 Platonides wrote:
> On 24/03/12 21:36, Max Semenik wrote:
>> And these graphs don't make any sense:
>> https://graphite.wikimedia.org/dashboard/MobileFrontend-DOMParse
>> the whole function's execution time is much larger than sum of its
>> pieces. What's going on?
> Maybe it'
On 24/03/12 21:36, Max Semenik wrote:
> And these graphs don't make any sense:
> https://graphite.wikimedia.org/dashboard/MobileFrontend-DOMParse
> the whole function's execution time is much larger than sum of its
> pieces. What's going on?
Maybe it's a recursive function?
I would have suspected
On 24.03.2012, 23:51 Patrick wrote:
> On Sat, Mar 24, 2012 at 12:33 PM, Patrick Reilly
> wrote:
>> On Sat, Mar 24, 2012 at 12:15 PM, Max Semenik wrote:
>>> On 24.03.2012, 20:16 Asher wrote:
>>>
There was also a the release of a majorly changed MobileFrontend earlier
that day / prior n
On Sat, Mar 24, 2012 at 12:33 PM, Patrick Reilly wrote:
> On Sat, Mar 24, 2012 at 12:15 PM, Max Semenik wrote:
>> On 24.03.2012, 20:16 Asher wrote:
>>
>>> There was also a the release of a majorly changed MobileFrontend earlier
>>> that day / prior night that line up with the first spike. The MF
On Sat, Mar 24, 2012 at 12:15 PM, Max Semenik wrote:
> On 24.03.2012, 20:16 Asher wrote:
>
>> There was also a the release of a majorly changed MobileFrontend earlier
>> that day / prior night that line up with the first spike. The MF rewrite
>> doesn't perform well - MobileFrontend::DOMParse avg
On 24.03.2012, 20:16 Asher wrote:
> There was also a the release of a majorly changed MobileFrontend earlier
> that day / prior night that line up with the first spike. The MF rewrite
> doesn't perform well - MobileFrontend::DOMParse avg time went from 15ms to
> 150ms (~500ms at 99th) and it woul
Hi.
There are over a dozen reports of general slowness with the English
Wikipedia:
https://en.wikipedia.org/w/index.php?oldid=483631204#is_it_me_or_is_wiki_ver
y_slow.3F
As I browsed and edited the site today, I experienced similar issues
(painful slowness on intermittent page loads, loading hal
