Conversation

Notices

1. Embed this notice
   Ayo (ayo@lonely.town)'s status on Saturday, 03-Aug-2024 02:46:16 JST Ayo

   The good news, compiling libzstd with ZSTD_LIB_MINIFY=1 brings it down to 164k while still easily beating zlib (100k) in terms of performance and ratio.

   The bad news, 164k is still pretty significant on the ncdu static binary:

   582k ncdu-2.5
   601k ncdu-new-nocompress
   765k ncdu-new-zstd

   Let's see if I can find other sources of bloat to throw away. :blobshrug:

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Wolf480pl (wolf480pl@mstdn.io)'s status on Saturday, 03-Aug-2024 02:58:53 JST Wolf480pl

     in reply to

     @ayo hmm 765k sounds big indeed. You wouldn't be able to fit two ncdus on a floppy

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 03-Aug-2024 03:00:39 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @ayo What's zstd/zlib for in the case of ncdu though? (I'm still on the C version)
   • Embed this notice
     Ayo (ayo@lonely.town)'s status on Saturday, 03-Aug-2024 03:04:29 JST Ayo

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan Working on a new export format that supports parallel export and random-access browsing without loading the entire directory tree into memory. Could work without compression, but that's somewhat more of a waste of disk space than a larger binary.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Ayo (ayo@lonely.town)'s status on Sunday, 04-Aug-2024 14:45:25 JST Ayo

     in reply to

     10 more of these and I'll have compensated for my choice of zstandard. :blobcatsweat:
     https://g.blicky.net/ncdu.git/commit/?id=90b43755b87ffe771e40a2ffbe70d4fe9ed15628

     Haelwenn /элвэн/ :triskell: likes this.