On Mon, 2022-01-10 at 05:56 -0800, Felix Lechner wrote: > Hi, > > On Mon, Jan 10, 2022 at 5:45 AM Ben Hutchings <b...@decadent.org.uk> wrote: > > > > lintian allocated about 23 GiB > > Thanks for reporting this! > > That is one of several mysterious results of what happened when I > simplified the code. It's possibly due to excessive regex usage,
I'm not aware of regex processing ever requiring lots of memory. > although Perl usually catches that. Another possibility is an > accidental recursion in Lintian's copy of your package's file index. > Either way, I will shortly add helpful profiling information that you > will be able to examine on our website. I don't really want to examine it, I want you or some other lintian contributor to fix it. > On the positive side, I broke Lintian's 23 original checks into 353 > pieces (and counting). It makes issues much easier to monitor and > isolate. OK, but it's no longer working for me or probably anyone working on a larger package. I just tested with some older releases. The performance got worse between buster and bullseye, but the bullseye version is still usable for me (~ 1.3 GiB VM used, 17 min wallclock time). So the regression is since bullseye. Ben. -- Ben Hutchings I say we take off; nuke the site from orbit. It's the only way to be sure.
signature.asc
Description: This is a digitally signed message part
