Mailinglist Archive: opensuse (1212 mails)

< Previous Next >
Re: [opensuse] Performance of "cut" and "uniq"
On Fri, 27 Apr 2012 20:24:32 -0700, Jeff Janes <jeff.janes@xxxxxxxxx>

The difference in performance is erased by setting LANG=C (the default
is en_US.UTF-8), which change makes the installed binary much faster
but doesn't change the built-from-source binary performance. See
examples below.

That's to be expected. Many distributions (I know of at least Fedora
and Arch Linux besides SUSE) use a patch that teaches the coreutils
how to handle multibyte locales. The downside is that multibyte
processing slows down the utils.

Is it a known issue that building from source lets the CPU safely take
advantage of short-cuts to make things faster even under UTF-8 that a
packaged binary cannot? Or perhaps is there a bug in the
build-from-source that makes it faster, but somehow unsafe for UTF-8?

Something's wrong if you get different results from a binary package
vs. binaries built by building your owen rpm.

If you do not use our spec file and the patches we supply it's no
wonder you get faster binaries. So the real question is, how did you
build the binaries precisely.

If you built the package locally by using build, there should be no

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups