Takashi Iwai <tiwai@suse.de> wrote:
And cpio takes also so long... It's no CPU-bound, and it's waiting for the inputs?
GNU cpio is slow. star is almost two times faster than the cpio implementation typically used on Linux. You may either use "spcio", "star cli=cpio ..." or "star" and there are two main features from star that make it faster: - star forks into two processes: one for archive handling and one as the filesystem interface. Both are coupled via a shared memory used as FIFO and decouples reading/writing the archive from writing/reading to/from the filesystem. - As a result of the FIFO, star uses larger I/O sizes to reduce the filesystem overhead from the kernel. If you like to compare results, it makes sense to check the options fs= for larger FIFO size and -no-fsync to make star as unreliable as GNU tar or GNU cpio which is important for comparison on Linux with it's ineffective filesystem cache that slows down with fsync() calls. If star is run in cpio CLI compatibility, it enables -no-fsync and -install. The option -install implements AT&T cpio compatibility that allows to "overwrite" existing binaries without causing the an old running copy to dump core. Since the latter AT&T feature is not documented, this is not part of the gcpio implementation. Do you know how Linux package managers handle this situation? Jörg -- EMail:joerg@schily.net Jörg Schilling D-13353 Berlin Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/