File Sink Unbuffered

I noticed a large difference in errors between input and output files
when
I turn unbuffered on and off.

With unbuffered on, there was no difference between my input and output
file.

With unbuffered off, there were a lot of small errors that were
introduced
to the output file.

Is this a known issue, and should I always keep unbuffered on? gr3.7.6
ubuntu 14.04

v/r,
Rich

On 03/23/2015 08:27 PM, Richard B. wrote:

ubuntu 14.04

v/r,
Rich


Discuss-gnuradio mailing list
[email protected]lid
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
If you unceremoniously terminate your flow-graph, there will be data in
‘stdio’ buffers that have not yet been committed to the operating
system.

It may be the case, given Gnu Radio’s internal buffering mechanism, that
using “unbuffered” all the time is the right thing to do, unless stdio
buffers offer a performance advantage for an application (Gnu Radio,
in this case) that already does alot of its own buffering.

Thanks. I’m having trouble recreating the error so I think I want to
take
this back. I don’t see a difference anymore between buffered and
unbuffered. I had multiple instances of gr open and running when I
noticed
the difference. Call it a fluke.

Rich

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs