I have created repo for linux 5.x series kernel. And successfully created three records from incremental patches:

5.0 -> 5.0.1 -> 5.0.2

Repo dir is 1.6GB in sum for 67K files.

One small (?) issue is pijul log eats 1.3GB of RAM to show three records, rest command’s memory appetites are OK in general. For example:

• pijul rec -am"." on not (!) modified repo eats only 200MB;
• pijul diff --short on modified repo eats only 200MB;
• pijul rec -am"5.0.2" after applied patch to file tree eats only 200MB;
• pijul add -r * eats nothing after applied patch and longest run operation;

Thanks! This is because it loads up the entire patch in memory. That’s quite naive and could be easily fixed.

Could be pijul add -r * made be run faster?

Attention, you broken db access right now:

$ pijul log
# press q to exit editor
$ pijul log --hash-only
Error: Pristine locked
$

I wasn’t patient enough to wait for pijul add -r to complete on the linux kernel sources, so I fixed it. Now I don’t have the time to hit ctrl+c.

Oh, and I just tested, pijul log with the first initial giant patch takes 9Mb now. Thanks a lot for this test! It was super helpful.

Testing.

Now when applied new patch to linux kernel tree cant to add:

$ pi add -r *
Error: File already in repository: arch

Before it silently run thru all tree without fatal break.

Fixed.

Will you make performance boost for other commands too?

• pijul diff
• pijul record -am“patch 5.0.7 applied“

Lets skip for now slow pull and push commands on nest and count it cant handle such huge traffic.

I’d love to. One of the things I could do is to use the modification times, but that’s quite tricky.

Just do pijul diff in multi core way how you did for add and rest add to your road map for next year.