[17:35:12] TIL someone made an Excimer integration to OpenTelemetry and Grafana Pyroscope: https://github.com/excimetry/excimetry [17:37:23] I noticed after bd808 was chatting with someone about it in #mediawiki that it was added to https://www.mediawiki.org/wiki/Excimer [17:43:52] Krinkle: by the way, what exactly did i sign up for in https://phabricator.wikimedia.org/T400109 ? i hope it's mostly rubber-stamping work you're planning to do, since i have a few things going on [17:44:45] (i've read that task and a few of the links, i had no idea that we're using anything other than excimer in production. i thought it took over everything.) [17:45:34] I wanted someone else in the team to do it, to share knowledge and to verify that it isn't just "works for $me" where $me = Krinkle. [17:45:46] But we can do that next week perhaps outside the critical path. [17:46:16] Yeah, that's a useful realization RE: Not just Excimer. [17:47:13] Excimer is a sampling profiler so concerned with latency / time spent only. It will miss the majority of small function calls, and so won't e.g. measure function call counts or memory usage, which is the kind of thing we use XHProf/XHGui for. [17:49:25] which can be used via WikimediaDebug ("XHGui" or "plain text profile"), the latter which uses the core Profiler class and appends a comment with function call counts, and works on HTML/CSS/JS and on CLI. [17:49:51] I'd be intersting to one-day support Excimer via CLI. [17:50:16] but not yet, at least not in prod. [17:51:57] mhm