Using syswrite over write only means that Perl won't do any buffering. Your operating system will still do buffering, likely until the file gets closed or the process calls exit.

I guess you can only show the "real" progress as the OS claims by waiting until your program finishes and then calculating the throughput.

As an aside, you might want to unbuffer STDOUT so your progress gets displayed:

$|++;

[download]

(unless you're already doing that somewhere). If you're concerned about writing speed, I'd try to write larger buffers, maybe something in the range of the cluster size of the hard disk or in the range of half/twice the cache size of the hard disk to maximize the amount of data available for the disk to write.

In reply to Re: FILE IO, delay after finish. by Corion
in thread FILE IO, delay after finish. by exodist

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.