You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the same way that there already is a flow to generate a ZIP archive it would be nice to have the same for a simple (uncompressed) TAR ball.
Details
I already have some working code taken from one of my personal projects (see https://github.com/choffmeister/alpakka/tree/tarball-flow). The implementation is pretty straight forward. When one does not need compression (which still could be applied afterwards, like .tar -> .tar.gz), it has one big benefit over the ZIP archive stream:
It does not rely on the blocking Java Input/OutputStream API, but instead it directly uses akka.util.ByteString. So it seems to be way more efficient in terms of CPU usage (in some tests of mine I found 50% usage vs 3% CPU usage when comparing uncompressed ZIP stream vs my TAR stream).
Of course this should be integrated into the already existing Archive class. But before I invest more time to make the code fit nicely into the existing code base, I would like to know if such a feature would be merged.
The text was updated successfully, but these errors were encountered:
Short description
In the same way that there already is a flow to generate a ZIP archive it would be nice to have the same for a simple (uncompressed) TAR ball.
Details
I already have some working code taken from one of my personal projects (see https://github.com/choffmeister/alpakka/tree/tarball-flow). The implementation is pretty straight forward. When one does not need compression (which still could be applied afterwards, like
.tar
->.tar.gz
), it has one big benefit over the ZIP archive stream:It does not rely on the blocking Java Input/OutputStream API, but instead it directly uses akka.util.ByteString. So it seems to be way more efficient in terms of CPU usage (in some tests of mine I found 50% usage vs 3% CPU usage when comparing uncompressed ZIP stream vs my TAR stream).
Of course this should be integrated into the already existing
Archive
class. But before I invest more time to make the code fit nicely into the existing code base, I would like to know if such a feature would be merged.The text was updated successfully, but these errors were encountered: