Compare file compression methods by sending to /dev/null

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I'd like to compare the time to completion for compression algorithms and parameters. I'm confident that the inputs will be set up properly. In order to save space and avoid some variability my thought is to just send output to /dev/null. What are downsides in this situation?










share|improve this question

















  • 1





    then yes just use time comand > /dev/null if results are just time based. like ` time tar cvf /dev/null Pictures/png/` here goes : ` Pictures/png/rcrrcrncrcnz.png real 0m0.011s user 0m0.000s sys 0m0.004s`

    – francois P
    Mar 11 at 19:15







  • 2





    The downside is that you can't time the uncompression speeds.

    – Kusalananda
    Mar 11 at 19:30











  • Another downside is that you will not get the size (compression ratio) unless you pipe the output via something that will show the size, for example dd (which will also show the time used).

    – sudodus
    Mar 11 at 19:53

















0















I'd like to compare the time to completion for compression algorithms and parameters. I'm confident that the inputs will be set up properly. In order to save space and avoid some variability my thought is to just send output to /dev/null. What are downsides in this situation?










share|improve this question

















  • 1





    then yes just use time comand > /dev/null if results are just time based. like ` time tar cvf /dev/null Pictures/png/` here goes : ` Pictures/png/rcrrcrncrcnz.png real 0m0.011s user 0m0.000s sys 0m0.004s`

    – francois P
    Mar 11 at 19:15







  • 2





    The downside is that you can't time the uncompression speeds.

    – Kusalananda
    Mar 11 at 19:30











  • Another downside is that you will not get the size (compression ratio) unless you pipe the output via something that will show the size, for example dd (which will also show the time used).

    – sudodus
    Mar 11 at 19:53













0












0








0








I'd like to compare the time to completion for compression algorithms and parameters. I'm confident that the inputs will be set up properly. In order to save space and avoid some variability my thought is to just send output to /dev/null. What are downsides in this situation?










share|improve this question














I'd like to compare the time to completion for compression algorithms and parameters. I'm confident that the inputs will be set up properly. In order to save space and avoid some variability my thought is to just send output to /dev/null. What are downsides in this situation?







compression null






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 11 at 19:13









Aaron ThomasAaron Thomas

1244




1244







  • 1





    then yes just use time comand > /dev/null if results are just time based. like ` time tar cvf /dev/null Pictures/png/` here goes : ` Pictures/png/rcrrcrncrcnz.png real 0m0.011s user 0m0.000s sys 0m0.004s`

    – francois P
    Mar 11 at 19:15







  • 2





    The downside is that you can't time the uncompression speeds.

    – Kusalananda
    Mar 11 at 19:30











  • Another downside is that you will not get the size (compression ratio) unless you pipe the output via something that will show the size, for example dd (which will also show the time used).

    – sudodus
    Mar 11 at 19:53












  • 1





    then yes just use time comand > /dev/null if results are just time based. like ` time tar cvf /dev/null Pictures/png/` here goes : ` Pictures/png/rcrrcrncrcnz.png real 0m0.011s user 0m0.000s sys 0m0.004s`

    – francois P
    Mar 11 at 19:15







  • 2





    The downside is that you can't time the uncompression speeds.

    – Kusalananda
    Mar 11 at 19:30











  • Another downside is that you will not get the size (compression ratio) unless you pipe the output via something that will show the size, for example dd (which will also show the time used).

    – sudodus
    Mar 11 at 19:53







1




1





then yes just use time comand > /dev/null if results are just time based. like ` time tar cvf /dev/null Pictures/png/` here goes : ` Pictures/png/rcrrcrncrcnz.png real 0m0.011s user 0m0.000s sys 0m0.004s`

– francois P
Mar 11 at 19:15






then yes just use time comand > /dev/null if results are just time based. like ` time tar cvf /dev/null Pictures/png/` here goes : ` Pictures/png/rcrrcrncrcnz.png real 0m0.011s user 0m0.000s sys 0m0.004s`

– francois P
Mar 11 at 19:15





2




2





The downside is that you can't time the uncompression speeds.

– Kusalananda
Mar 11 at 19:30





The downside is that you can't time the uncompression speeds.

– Kusalananda
Mar 11 at 19:30













Another downside is that you will not get the size (compression ratio) unless you pipe the output via something that will show the size, for example dd (which will also show the time used).

– sudodus
Mar 11 at 19:53





Another downside is that you will not get the size (compression ratio) unless you pipe the output via something that will show the size, for example dd (which will also show the time used).

– sudodus
Mar 11 at 19:53










0






active

oldest

votes












Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505708%2fcompare-file-compression-methods-by-sending-to-dev-null%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505708%2fcompare-file-compression-methods-by-sending-to-dev-null%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?