> I recently set up a Core 2 duo system. Following the AMD64 howto, the > system now works. Kernel compilation took 1:40 minutes passing -j6 to > make. > > Then I tried to bunzip a large file and found out that the machine was > about 40 % in idle which is clear because bzip2 is only one process. > So is there any way to build those utilities like bzip2 or gzip in a > thread-using way? It's not that nice to see the machine in idle at > all^^ Maybe there's any hidden use flag I haven't heard of or so :)
I think, that is a misconception within bzip2. The alternative would be: - decompress one chunk, and write it to the stdout while the next block is already being decompressed. - compress a chunk, while reading the next one from stdin That would eat up at least twice the memory as it does now. And after i searched portage, i found "pbzip2" - what about that? It may solve your problems ;-)
signature.asc
Description: OpenPGP digital signature