use gzip in a subprocess on unix
Bug #425499 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Fast Import |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rather than using gzip file and doing a seek(0), fast-import could:
- use gzip in a subprocess
- reopen the process to start over
I suspect this would be faster on mp machines, due to freeing up an
entire CPU to do decompression. !citation needed of course.
affects bzr-fastimport
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkq
/GQAnR2I2EIxCw7
=M31S
-----END PGP SIGNATURE-----
Changed in bzr-fastimport: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
To post a comment you must log in.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert Collins wrote:
> Public bug reported:
>
> Rather than using gzip file and doing a seek(0), fast-import could:
> - use gzip in a subprocess
> - reopen the process to start over
>
> I suspect this would be faster on mp machines, due to freeing up an
> entire CPU to do decompression. !citation needed of course.
>
> affects bzr-fastimport
>
I should also mention that gzip.GzipFile( open('foo. gz')).read( ) is often ]).stdout. read()
slower than Popen(['gzip foo.gz'
I don't remember all the details, but I do remember benchmarking that
sort of thing. (I believe this was even on a single processor machine.)
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkq mZocACgkQJdeBCY SNAAOE1QCgvXnjC O+YoDPUgh360Amn pw2B RzkUYeCGdFZ/ vWmDG
kzgAoIO6FKNIz7a
=4h8j
-----END PGP SIGNATURE-----