On Sat, 2004-07-24 at 13:24, Sindre Pedersen Bjordal wrote: > lør, 24.07.2004 kl. 13.01 skrev Ralf Corsepius: > > On Fri, 2004-07-23 at 22:24, seth vidal wrote: > > > On Fri, 2004-07-23 at 15:54 +0200, Matias Feliciano wrote: > > > > Le ven 23/07/2004 à 07:13, seth vidal a écrit : > > > > > [...] > > > > > http://linux.duke.edu/metadata/generate/createrepo-0.3.4.tar.gz > > > > > http://linux.duke.edu/metadata/generate/createrepo-0.3.4-1.src.rpm > > > > > > > > > > [...] > > > > > primary.xml.gz - this holds the primary metadata for the packages > > > > > (names, summary, requires, provides, deps, etc) > > > > > > > > bzip2 instead of gzip ? > > > > apt use bzip2. > > > > > > > > > > bzip2 is more processor intensive > > apt uses bzip2 for its repositories for quite a while. The processor > > load this had introduced had never been an actual problem. Conversely, > > users on low bandwith connections had appreciated it. > > > > Ralf > > > > Just out of curiosity, how big a difference does bz2 make in compression On createrepo generated *.xml files the difference in file size is ca. factor 1.4 to 1.8 > and increase of processor load? Noticeable, but far from being critical: Bunzip'ing a createrepo generated repo of FC1 (>3000 entries), on a PIII/1GHz w/ FC1: real 0m1.587s user 0m1.440s sys 0m0.090s Gunzip'ing the same repo: # time gunzip *gz real 0m0.230s user 0m0.130s sys 0m0.050s => ca. factor 10. Note, this is "~0.2s" vs. "~2s", so this difference won't hardly be noticed by users. Ralf
