Date: Tue, 13 Mar 2018 21:13:23 +0000
From: =?utf-8?B?Q8OhZw==?= <ca6c@bitmessage.ch>
To: alpine-user@lists.alpinelinux.org
Subject: Re: [alpine-user] FYI: community/zstd binary much (up to 4x)
 slower than necessary
Message-ID: <20180313211323.aFXkP%ca6c@bitmessage.ch>
References: <20180313180648.kXWsR%steffen@sdaoden.eu>
In-Reply-To: <20180313180648.kXWsR%steffen@sdaoden.eu>
Mail-Followup-To: alpine-user@lists.alpinelinux.org,
 =?utf-8?B?Q8OhZw==?= <ca6c@bitmessage.ch>
User-Agent: s-nail v14.9.9
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Steffen Nurpmeso wrote:

> Hello, for your possible interest.
>=20
> In a thead for the LUGA(ustria) i eventually had to time some
> compression algorithms and wondered why zstd is so slow, but
> especially so the decompressing stage, which a key feature of this
> one.  It turns out that the -Os compilation causes, well, drama-
> tical performance degradation.  I compiled my own with -O3 and the
> difference is up to factor four.  Just one example:

What about -O2? Also what are the differences in binary sizes? Are you
using gcc? If yes, try clang.

--
ca=C3=B3c



---
Unsubscribe:  alpine-user+unsubscribe@lists.alpinelinux.org
Help:         alpine-user+help@lists.alpinelinux.org
---