#zstd — Public Fediverse posts

Creating .tar.zst archives on Windows doesn’t require extra software. The native tar command already supports Zstandard (zstd). Simply add the context menu option to get started: github.com/SamiLehtinen... #Windows #Zstandard #Zstd #compression

GitHub - SamiLehtinen/Compress...

Creating .tar.zst archives on Windows doesn’t require extra software. The native tar command already supports Zstandard (zstd). Simply add the context menu option to get started: https://github.com/SamiLehtinen/CompressTarZstd #Windows #Zstandard #Zstd #compression

Creating .tar.zst archives on Windows doesn’t require extra software. The native tar command already supports Zstandard (zstd). Simply add the context menu option to get started: https://github.com/SamiLehtinen/CompressTarZstd #Windows #Zstandard #Zstd #compression

Creating .tar.zst archives on Windows doesn’t require extra software. The native tar command already supports Zstandard (zstd). Simply add the context menu option to get started: https://github.com/SamiLehtinen/CompressTarZstd #Windows #Zstandard #Zstd #compression

Creating .tar.zst archives on Windows doesn’t require extra software. The native tar command already supports Zstandard (zstd). Simply add the context menu option to get started: https://github.com/SamiLehtinen/CompressTarZstd #Windows #Zstandard #Zstd #compression

Software developer Steven Geisel highlights one of the new features of up and coming .NET 11, which is a ready-to-use implementation of the Zstd compression algorithm (https://github.com/facebook/Zstd).

Published by Facebook in 2018 as RFC 8478, Zstd is a high performance, lossless compression algorithm that can produce close to instant results under certain configurations.

"Zstandard compression in .NET 11"

https://steven-giesel.com/blogPost/6066abb6-640a-4225-ac33-3f4d5a1a1d16

#dotnet #csharp #zstd #programming #algorithms #compression

Software developer Steven Geisel highlights one of the new features of up and coming .NET 11, which is a ready-to-use implementation of the Zstd compression algorithm (https://github.com/facebook/Zstd).

Published by Facebook in 2018 as RFC 8478, Zstd is a high performance, lossless compression algorithm that can produce close to instant results under certain configurations.

"Zstandard compression in .NET 11"

https://steven-giesel.com/blogPost/6066abb6-640a-4225-ac33-3f4d5a1a1d16

#dotnet #csharp #zstd #programming #algorithms #compression

Software developer Steven Geisel highlights one of the new features of up and coming .NET 11, which is a ready-to-use implementation of the Zstd compression algorithm (https://github.com/facebook/Zstd).

Published by Facebook in 2018 as RFC 8478, Zstd is a high performance, lossless compression algorithm that can produce close to instant results under certain configurations.

"Zstandard compression in .NET 11"

https://steven-giesel.com/blogPost/6066abb6-640a-4225-ac33-3f4d5a1a1d16

#dotnet #csharp #zstd #programming #algorithms #compression

Software developer Steven Geisel highlights one of the new features of up and coming .NET 11, which is a ready-to-use implementation of the Zstd compression algorithm (https://github.com/facebook/Zstd).

Published by Facebook in 2018 as RFC 8478, Zstd is a high performance, lossless compression algorithm that can produce close to instant results under certain configurations.

"Zstandard compression in .NET 11"

https://steven-giesel.com/blogPost/6066abb6-640a-4225-ac33-3f4d5a1a1d16

#dotnet #csharp #zstd #programming #algorithms #compression

Software developer Steven Geisel highlights one of the new features of up and coming .NET 11, which is a ready-to-use implementation of the Zstd compression algorithm (https://github.com/facebook/Zstd).

Published by Facebook in 2018 as RFC 8478, Zstd is a high performance, lossless compression algorithm that can produce close to instant results under certain configurations.

"Zstandard compression in .NET 11"

https://steven-giesel.com/blogPost/6066abb6-640a-4225-ac33-3f4d5a1a1d16

#dotnet #csharp #zstd #programming #algorithms #compression

Heute kam ich endlich das zu final #http3 und #zstd #compression bei meinem #Wordpress #Blog in Betrieb zu nehmen.

Bei dem Umstieg von den sury.org Paketen auf die offiziellen #nginx Pakete gab es ein paar Probleme, wodurch ich einige Wochen ohne #http3 auskommen musste.

Ich hoffe das nun alles stabil läuft. Bisher rennt aber alles und hat #myhomezone noch einen Tick schneller gemacht.

Wer einmal testen möchte, kann gerne auf meinem #Blog vorbei schauen.

https://www.myhome.zone

Heute kam ich endlich das zu final #http3 und #zstd #compression bei meinem #Wordpress #Blog in Betrieb zu nehmen.

Bei dem Umstieg von den sury.org Paketen auf die offiziellen #nginx Pakete gab es ein paar Probleme, wodurch ich einige Wochen ohne #http3 auskommen musste.

Ich hoffe das nun alles stabil läuft. Bisher rennt aber alles und hat #myhomezone noch einen Tick schneller gemacht.

Wer einmal testen möchte, kann gerne auf meinem #Blog vorbei schauen.

https://www.myhome.zone

Heute kam ich endlich das zu final #http3 und #zstd #compression bei meinem #Wordpress #Blog in Betrieb zu nehmen.

Bei dem Umstieg von den sury.org Paketen auf die offiziellen #nginx Pakete gab es ein paar Probleme, wodurch ich einige Wochen ohne #http3 auskommen musste.

Ich hoffe das nun alles stabil läuft. Bisher rennt aber alles und hat #myhomezone noch einen Tick schneller gemacht.

Wer einmal testen möchte, kann gerne auf meinem #Blog vorbei schauen.

https://www.myhome.zone

Heute kam ich endlich das zu final #http3 und #zstd #compression bei meinem #Wordpress #Blog in Betrieb zu nehmen.

Bei dem Umstieg von den sury.org Paketen auf die offiziellen #nginx Pakete gab es ein paar Probleme, wodurch ich einige Wochen ohne #http3 auskommen musste.

Ich hoffe das nun alles stabil läuft. Bisher rennt aber alles und hat #myhomezone noch einen Tick schneller gemacht.

Wer einmal testen möchte, kann gerne auf meinem #Blog vorbei schauen.

https://www.myhome.zone

#WinRAR 7.22 has been released (#RAR / #ZIP / #ZIPX / #7Zip / #7z / #GZip / #zstd / #Zstandard / #FileArchiver / #DataCompression / #DarkMode) https://rarlab.com/

#WinRAR 7.22 has been released (#RAR / #ZIP / #ZIPX / #7Zip / #7z / #GZip / #zstd / #Zstandard / #FileArchiver / #DataCompression / #DarkMode) https://rarlab.com/

#WinRAR 7.22 has been released (#RAR / #ZIP / #ZIPX / #7Zip / #7z / #GZip / #zstd / #Zstandard / #FileArchiver / #DataCompression / #DarkMode) https://rarlab.com/

maxpack: межфайловая дедупликация на версионных данных

Разбор межфайловой дедупликации на версионных данных: почему обычная упаковка упирается в потолок и что меняется на CPython, Go и Node.js.

https://habr.com/ru/articles/1019718/

#сжатие_данных #дедупликация #архивация #versioned_data #tar #zstd #7z #snapshots

maxpack: межфайловая дедупликация на версионных данных

Разбор межфайловой дедупликации на версионных данных: почему обычная упаковка упирается в потолок и что меняется на CPython, Go и Node.js.

https://habr.com/ru/articles/1019718/

#сжатие_данных #дедупликация #архивация #versioned_data #tar #zstd #7z #snapshots

maxpack: межфайловая дедупликация на версионных данных

Разбор межфайловой дедупликации на версионных данных: почему обычная упаковка упирается в потолок и что меняется на CPython, Go и Node.js.

https://habr.com/ru/articles/1019718/

#сжатие_данных #дедупликация #архивация #versioned_data #tar #zstd #7z #snapshots

maxpack: межфайловая дедупликация на версионных данных

Разбор межфайловой дедупликации на версионных данных: почему обычная упаковка упирается в потолок и что меняется на CPython, Go и Node.js.

https://habr.com/ru/articles/1019718/

#сжатие_данных #дедупликация #архивация #versioned_data #tar #zstd #7z #snapshots

Oh, my #ccache is filling up:

Cache size (GiB): 40.3 / 100.0 (40.25%)

Note that this is #zstd compressed.

#dev

Oh, my #ccache is filling up:

Cache size (GiB): 40.3 / 100.0 (40.25%)

Note that this is #zstd compressed.

#dev

Oh, my #ccache is filling up:

Cache size (GiB): 40.3 / 100.0 (40.25%)

Note that this is #zstd compressed.

#dev

Oh, my #ccache is filling up:

Cache size (GiB): 40.3 / 100.0 (40.25%)

Note that this is #zstd compressed.

#dev

Oh, my #ccache is filling up:

Cache size (GiB): 40.3 / 100.0 (40.25%)

Note that this is #zstd compressed.

#dev

@davidculley so what? Actually, many contributions from #meta #facebook to #opensource world including #MySQL. #RocksDB born there. And don't forget #zstd.

@davidculley so what? Actually, many contributions from #meta #facebook to #opensource world including #MySQL. #RocksDB born there. And don't forget #zstd.

@davidculley so what? Actually, many contributions from #meta #facebook to #opensource world including #MySQL. #RocksDB born there. And don't forget #zstd.

@davidculley so what? Actually, many contributions from #meta #facebook to #opensource world including #MySQL. #RocksDB born there. And don't forget #zstd.

@davidculley so what? Actually, many contributions from #meta #facebook to #opensource world including #MySQL. #RocksDB born there. And don't forget #zstd.

My new daily backup script, pg_dump with zstd compression level 19.

docker exec \
   ak-postgres-1 \
   pg_dump -U umeyashiki umeyashiki_akkoma | \
   nice -n 19 \
   ionice -c 3 \
   chrt --idle 0 \
   zstd -T0 -19 --rsyncable -q > "$BACKUP_DIR/db_latest.sql.zst";

Today I learned something new about the scheduling priority. Since zstd compression is very CPU-intensive, set it to low priority so it doesn’t slow the entire system down during compression.

Commands that precede zstd here are:

• nice -n 19 [cmd]
• ionice -c 3 [cmd]
• chrt --idle 0 [cmd]

By chaining nice, ionice, and chrt together before the zstd command, the script forces the compression process to run with the absolute lowest possible priority for both the CPU and the disk.

• nice 19 is the lowest priority CPU priority.
• ionice with class 3 means idle. A program running with idle I/O priority will only get disk time when no other program has asked for disk I/O for a defined grace period.
• chrt --idle 0: Set scheduling policy to SCHED_IDLE (scheduling very low priority jobs).

References:

• man 1 chrt
• man 1 nice
• man 1 ionice

#linux #docker #zstd #postgresql #sched

My new daily backup script, pg_dump with zstd compression level 19.

docker exec \
   ak-postgres-1 \
   pg_dump -U umeyashiki umeyashiki_akkoma | \
   nice -n 19 \
   ionice -c 3 \
   chrt --idle 0 \
   zstd -T0 -19 --rsyncable -q > "$BACKUP_DIR/db_latest.sql.zst";

Today I learned something new about the scheduling priority. Since zstd compression is very CPU-intensive, set it to low priority so it doesn’t slow the entire system down during compression.

Commands that precede zstd here are:

• nice -n 19 [cmd]
• ionice -c 3 [cmd]
• chrt --idle 0 [cmd]

By chaining nice, ionice, and chrt together before the zstd command, the script forces the compression process to run with the absolute lowest possible priority for both the CPU and the disk.

• nice 19 is the lowest priority CPU priority.
• ionice with class 3 means idle. A program running with idle I/O priority will only get disk time when no other program has asked for disk I/O for a defined grace period.
• chrt --idle 0: Set scheduling policy to SCHED_IDLE (scheduling very low priority jobs).

References:

• man 1 chrt
• man 1 nice
• man 1 ionice

#linux #docker #zstd #postgresql #sched

My new daily backup script, pg_dump with zstd compression level 19.

docker exec ak-postgres-1 pg_dump -U umeyashiki umeyashiki_akkoma \
  | nice -n 19 ionice -c 3 chrt --idle 0 zstd -T0 -19 --rsyncable -q > "$BACKUP_DIR/db_latest.sql.zst";

Today I learned something new about the scheduling priority. Since zstd compression is very CPU-intensive, set it to low priority so it doesn’t slow the entire system down during compression.

Commands that precede zstd here are:

• nice -n 19 [cmd]
• ionice -c 3 [cmd]
• chrt --idle 0 [cmd]

By chaining nice, ionice, and chrt together before the zstd command, the script forces the compression process to run with the absolute lowest possible priority for both the CPU and the disk.

• nice 19 is the lowest priority CPU priority.
• ionice with class 3 means idle. A program running with idle I/O priority will only get disk time when no other program has asked for disk I/O for a defined grace period.
• chrt --idle 0: Set scheduling policy to SCHED_IDLE (scheduling very low priority jobs).

References:

• man 1 chrt
• man 1 nice
• man 1 ionice

#linux #docker #zstd #postgresql #sched

My new daily backup script, pg_dump with zstd compression level 19.

docker exec \
   ak-postgres-1 \
   pg_dump -U umeyashiki umeyashiki_akkoma | \
   nice -n 19 \
   ionice -c 3 \
   chrt --idle 0 \
   zstd -T0 -19 --rsyncable -q > "$BACKUP_DIR/db_latest.sql.zst";

Today I learned something new about the scheduling priority. Since zstd compression is very CPU-intensive, set it to low priority so it doesn’t slow the entire system down during compression.

Commands that precede zstd here are:

• nice -n 19 [cmd]
• ionice -c 3 [cmd]
• chrt --idle 0 [cmd]

By chaining nice, ionice, and chrt together before the zstd command, the script forces the compression process to run with the absolute lowest possible priority for both the CPU and the disk.

• nice 19 is the lowest priority CPU priority.
• ionice with class 3 means idle. A program running with idle I/O priority will only get disk time when no other program has asked for disk I/O for a defined grace period.
• chrt --idle 0: Set scheduling policy to SCHED_IDLE (scheduling very low priority jobs).

References:

• man 1 chrt
• man 1 nice
• man 1 ionice

#linux #docker #zstd #postgresql #sched

My new daily backup script, pg_dump with zstd compression level 19.

docker exec \
   ak-postgres-1 \
   pg_dump -U umeyashiki umeyashiki_akkoma | \
   nice -n 19 \
   ionice -c 3 \
   chrt --idle 0 \
   zstd -T0 -19 --rsyncable -q > "$BACKUP_DIR/db_latest.sql.zst";

Today I learned something new about the scheduling priority. Since zstd compression is very CPU-intensive, set it to low priority so it doesn’t slow the entire system down during compression.

Commands that precede zstd here are:

• nice -n 19 [cmd]
• ionice -c 3 [cmd]
• chrt --idle 0 [cmd]

By chaining nice, ionice, and chrt together before the zstd command, the script forces the compression process to run with the absolute lowest possible priority for both the CPU and the disk.

• nice 19 is the lowest priority CPU priority.
• ionice with class 3 means idle. A program running with idle I/O priority will only get disk time when no other program has asked for disk I/O for a defined grace period.
• chrt --idle 0: Set scheduling policy to SCHED_IDLE (scheduling very low priority jobs).

References:

• man 1 chrt
• man 1 nice
• man 1 ionice

#linux #docker #zstd #postgresql #sched

Interesting blog post about text classification using compression, specifically the new "compression.zstd" module contributed by @emmatyping

https://maxhalford.github.io/blog/text-classification-zstd/

#compression #zstd #zstandard #classification

Interesting blog post about text classification using compression, specifically the new "compression.zstd" module contributed by @emmatyping

https://maxhalford.github.io/blog/text-classification-zstd/

#compression #zstd #zstandard #classification

Interesting blog post about text classification using compression, specifically the new "compression.zstd" module contributed by @emmatyping

https://maxhalford.github.io/blog/text-classification-zstd/

#compression #zstd #zstandard #classification

Interesting blog post about text classification using compression, specifically the new "compression.zstd" module contributed by @emmatyping

https://maxhalford.github.io/blog/text-classification-zstd/

#compression #zstd #zstandard #classification

Interesting blog post about text classification using compression, specifically the new "compression.zstd" module contributed by @emmatyping

https://maxhalford.github.io/blog/text-classification-zstd/

#compression #zstd #zstandard #classification

[Перевод] Пишем свой git: минимальная реализация на Rust

Контроль версий долгое время был для меня «чёрным ящиком»: я не понимал, как именно хранятся файлы, как формируются diff’ы и из чего состоят коммиты. А поскольку я люблю изобретать велосипеды, почему бы не попробовать реализовать git самому?

https://habr.com/ru/companies/cloud4y/articles/990052/

#git #rust #контроль_версий #sha256 #zstd #хеширование #petproject #системы_контроля_версий #объекты_git #commit

[Перевод] Пишем свой git: минимальная реализация на Rust

Контроль версий долгое время был для меня «чёрным ящиком»: я не понимал, как именно хранятся файлы, как формируются diff’ы и из чего состоят коммиты. А поскольку я люблю изобретать велосипеды, почему бы не попробовать реализовать git самому?

https://habr.com/ru/companies/cloud4y/articles/990052/

#git #rust #контроль_версий #sha256 #zstd #хеширование #petproject #системы_контроля_версий #объекты_git #commit

[Перевод] Пишем свой git: минимальная реализация на Rust

Контроль версий долгое время был для меня «чёрным ящиком»: я не понимал, как именно хранятся файлы, как формируются diff’ы и из чего состоят коммиты. А поскольку я люблю изобретать велосипеды, почему бы не попробовать реализовать git самому?

https://habr.com/ru/companies/cloud4y/articles/990052/

#git #rust #контроль_версий #sha256 #zstd #хеширование #petproject #системы_контроля_версий #объекты_git #commit

[Перевод] Пишем свой git: минимальная реализация на Rust

Контроль версий долгое время был для меня «чёрным ящиком»: я не понимал, как именно хранятся файлы, как формируются diff’ы и из чего состоят коммиты. А поскольку я люблю изобретать велосипеды, почему бы не попробовать реализовать git самому?

https://habr.com/ru/companies/cloud4y/articles/990052/

#git #rust #контроль_версий #sha256 #zstd #хеширование #petproject #системы_контроля_версий #объекты_git #commit

If you use #btrfs on kernels ranging from 6.12 to 6.19 and get the error:

VFS: Unable to mount root fs on unknown_block(0,0)

Add the 'btrfs' and 'microcode' hooks to /etc/mkinitcpio.conf via chroot and rerun initramfs generation.

If that doesn't help install `intel-ucode.img` and add it to your grub boot parameters in the initrd list.

If that still doesn't help (happens on Intel 3770k and older) disable #zstd initramfs compression, use gzip instead.

You are welcome

#initramfs #microcode

If you use #btrfs on kernels ranging from 6.12 to 6.19 and get the error:

VFS: Unable to mount root fs on unknown_block(0,0)

Add the 'btrfs' and 'microcode' hooks to /etc/mkinitcpio.conf via chroot and rerun initramfs generation.

If that doesn't help install `intel-ucode.img` and add it to your grub boot parameters in the initrd list.

If that still doesn't help (happens on Intel 3770k and older) disable #zstd initramfs compression, use gzip instead.

You are welcome

#initramfs #microcode

If you use #btrfs on kernels ranging from 6.12 to 6.19 and get the error:

VFS: Unable to mount root fs on unknown_block(0,0)

Add the 'btrfs' and 'microcode' hooks to /etc/mkinitcpio.conf via chroot and rerun initramfs generation.

If that doesn't help install `intel-ucode.img` and add it to your grub boot parameters in the initrd list.

If that still doesn't help (happens on Intel 3770k and older) disable #zstd initramfs compression, use gzip instead.

You are welcome

#initramfs #microcode

If you use #btrfs on kernels ranging from 6.12 to 6.19 and get the error:

VFS: Unable to mount root fs on unknown_block(0,0)

Add the 'btrfs' and 'microcode' hooks to /etc/mkinitcpio.conf via chroot and rerun initramfs generation.

If that doesn't help install `intel-ucode.img` and add it to your grub boot parameters in the initrd list.

If that still doesn't help (happens on Intel 3770k and older) disable #zstd initramfs compression, use gzip instead.

You are welcome

#initramfs #microcode

ZSTD with level MEDIUM gives you the same runtime as the traditional MS_XPRESS algorithm, but the backup is around 14 GB smaller. The level LOW is really fast (203 sec. vs. 305 sec., and the backups are still smaller (58 GB vs. 50 GB). #sqlserver #zstd #compression #performance