Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Stefan Bethke <stb@lassitu.de>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Additional stats
Date: Fri, 30 Oct 2026 12:15:58 +0100	[thread overview]
Message-ID: <87tsm3e8wh.wl-jch@irif.fr> (raw)
In-Reply-To: <121CCD01-E105-4A60-8BAA-1FDC7865F5C6@lassitu.de>

> here is my proposal: https://github.com/jech/galene/pull/349

Thanks, especially for mentioning explicitly that you used Claude to write
this code.

Unfortunately, your code has the typical flaws of LLM-generated code:

  - it's a single commit, with a verbose but useless commit message;

  - there are a number of changes that are unrelated to Prometheus, that
    are bundled into the same commit;

  - the comments are verbose and not useful;

  - the code is overly verbose, with no clear indication which features
    are actually useful;

  - doc strings and comments paraphrase the code rather than providing
    information that's useful to the reader.

For now, I suggest you extract the changes unrelated to Prometheus and
submit them in a separate PR.  Before we decide whether to work on
improving the code, I'd like to understand two things.

1. Do people actually feel that this kind of metrics are useful to include
   in Galene?  How do people use Prometheus usually, what insights does it
   give you, and are these insights useful?  Or do people just want
   Prometheus because it's what everyone does?

   (As far as I'm concerned, I optimise Galene by running it in production
   with profiling enabled, then spend some time poring over the profile.
   I find the output of a profiler much more useful, as it gives me
   a global view of the behaviour, not just the specific set of statistics
   that are exported by the monitoring interface.)

2. Are you actually using this code in production, and have you found the
   provided statistics useful for administering Galene?

Thanks again,

-- Juliusz

  reply	other threads:[~2026-10-30 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 11:19 [Galene] Additional stats Stefan Bethke
2026-10-20 14:15 ` [Galene] " Juliusz Chroboczek
2026-10-20 14:53   ` Sebastien Binet
2026-10-20 16:47     ` [Galene] GenAI in Galene [was:Additional stats] Juliusz Chroboczek
2026-10-29 18:44   ` [Galene] Re: Additional stats Stefan Bethke
2026-10-30 11:15     ` Juliusz Chroboczek [this message]
2026-10-30 11:55       ` Stefan Bethke
2026-10-30 12:46         ` Juliusz Chroboczek
2026-10-30 13:19           ` Stefan Bethke
2026-10-30 13:54             ` Juliusz Chroboczek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tsm3e8wh.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=galene@lists.galene.org \
    --cc=stb@lassitu.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox