I ported pigz from Unix to Windows
blog.kowalczyk.info
I ported pigz from Unix to Windows
1–10 of 34 posts
Re: I ported pigz from Unix to Windows
#2Worth mentioning that this is only of interest as technical info on porting process.
The port itself is very old and therefore very outdated.
Re: I ported pigz from Unix to Windows
#3This is clearly aimed at faster results in a single user desktop environment.
In a threaded server type app where available processor cores are already being utilized, I don't see much real advantage in this --- if any.
Re: I ported pigz from Unix to Windows
#4This is clearly aimed at faster results in a single user desktop environment. In a threaded server type app where available processor cores are already being utilized, I don't see much real advantage in this --- if any.
[deleted]
Re: I ported pigz from Unix to Windows
#5This is clearly aimed at faster results in a single user desktop environment. In a threaded server type app where available processor cores are already being utilized, I don't see much real advantage in this --- if any.
depends on the current load. i've worked places where we would create nightly postgres dumps via pg_dumpall, then pipe through pigz to compress. it's great if you run it when load is otherwise low and you want to squeeze every bit of performance out of the box during that quiet window.
this predates the maturation of pg_dump/pg_restore concurrency features :)
Re: I ported pigz from Unix to Windows
#6I wish premake could gain more traction.
It is the comprehensible alternative to Cmake etc.
Re: I ported pigz from Unix to Windows
#7Repository link: https://github.com/kjk/pigz
Re: I ported pigz from Unix to Windows
#8I wish premake could gain more traction. It is the comprehensible alternative to Cmake etc.
Xmake[0] is as-simple-as-premake and does IIRC everything Premake does and a whole lot more.
Re: I ported pigz from Unix to Windows
#9Worth mentioning that this is only of interest as technical info on porting process. The port itself is very old and therefore very outdated.
Perhaps it's worth it adding this as a note at the top of the post, maybe mentioning alternatives, such as an Actually Portable™ build of `pigz`[1] or just a windows build of zstd[2].
Re: I ported pigz from Unix to Windows
#10I recently ported WebKit's libpas memory allocator[1] to Windows, which used pthreads on the Linux and Darwin ports. Depending on what pthreads features you're using it's not that much code to shim to Windows APIs. It's around ~200 LOC[2] for WebKit's usage, which a lot smaller than pthread-win32.
[1] https://github.com/WebKit/WebKit/pull/41945 [2] https://github.com/WebKit/WebKit/blob/main/Source/bmalloc/li...