[17:03:05] Hey, is there a way to get flame graphs for wikidata only? [17:03:38] or build it for certain cases (similar to xhgui) [17:32:58] Amir1: kind of. You could filter a trace log file to a high level code path for wiki base [17:33:23] And then pass to flamegraph.pl [17:33:43] Like how we do for EditAction [17:34:29] Or even just a generic grep for "Wikibase" over index.log would probably get you quite far [17:35:09] oooh interesting [17:37:47] Krinkle: I don't have access to webperf1002.eqiad.wmnet to do it [17:37:54] am I missing something? [17:38:19] looking at https://wikitech.wikimedia.org/wiki/Performance/Runbook/Arc_Lamp_service [17:38:36] Also it might even suffice to use the interactive filter within an SVG. You can zoom in etc to whatever high level start method renders or does what you're interested in. [17:38:53] Yeah they're supposed to remain stateless [17:39:06] Use mwmaint or locally [17:39:19] files are on per.wm.o :) [17:40:17] hmm [17:40:20] let me play a bit [17:42:11] The only reason we created separate files for EditAction was that they made up a small and deep fraction of index.svg so when you zoom in, there is not much detail (we try to limit the size of the SVG to not be gigabytes to render). But might not be needed here, worth a try. Just using ctrl F in those graphs as-is and see what you get [18:50:17] Found the logs: https://performance.wikimedia.org/arclamp/logs/daily/ [18:50:23] I couldn't find it anywhere [18:56:28] gilles: the OKR meeting seems to be missing a video link [18:57:24] phedenskog: thanks, I'll add one [18:57:38] done [19:10:15] Amir1: ah ,sorry I thought that part was known. I understand the cofnusion now!