Dne 30. 05. 19 v 17:14 Peter Robinson napsal(a):
What about constrained systems where there's limited CPU, that could
be a container or a low end cloud instance without any guarantee of
resources or a Raspberry Pi.
Raspberry Pi is hard to measure. I'm getting quite random results due to
IO, I blame the on-board microSD card controller.
I tested following package set (podman + deps):
containernetworking-plugins-0.7.4-2.fc30.aarch64.rpm
containers-common-0.1.36-9.dev.gitd93a581.fc30.aarch64.rpm
criu-3.12-11.fc30.aarch64.rpm
fuse3-libs-3.5.0-1.fc30.aarch64.rpm
fuse-overlayfs-0.3-10.dev.gita7c8295.fc30.aarch64.rpm
libbsd-0.9.1-3.fc30.aarch64.rpm
libnet-1.1.6-17.fc30.aarch64.rpm
ostree-libs-2019.2-1.fc30.aarch64.rpm
podman-1.3.1-1.git7210727.fc30.aarch64.rpm
protobuf-c-1.3.1-2.fc30.aarch64.rpm
runc-1.0.0-93.dev.gitb9b6cc6.fc30.aarch64.rpm
slirp4netns-0.3.0-2.git4992082.fc30.aarch64.rpm
tar-1.32-1.fc30.aarch64.rpm
Then I re-compressed the RPMs by running:
rpmrebuild --define "%_binary_payload w19.zstdio" -p <pkg>
xz.2 size: 27M
zstd.19 size: 22M
Then I ran installs into ramdisk:
sync; echo 3 > /proc/sys/vm/drop_caches; time rpm -Uvh * --force
--nodeps --stats --noscripts --root=/tmp/foo
xz: 10.9s
zstd: 4.7s
When I installed RPMs on the system (micro SD card), it took approx.
1m30s in both cases, but it's really giving quite random results due to IO.
Zstd performs slightly better than xz, but users can hardly see any
difference, because of IO. Good thing is that it's almost equal and
doesn't degrade performance on low end hardware.
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
