So /dev/null works, I do not know what that really says about this though. Is there a difference between using dev/null and just running any non-disk-write flowgraph? Because I know I can run a flowgraph at 16 MS/s decimated to 8 MS/s, with never a single O even for hours of operation. With 16 GBytes of RAM one can't somehow in GR buffer up the 64 MBytes/sec data flow during one of those hiccups? What do all those "min output buffer" and "max output buffer" params on the advanced tabs of the blocks do? - John
On Thu, May 7, 2015 at 3:43 PM, <mle...@ripnet.com> wrote: > I looked at their blurb on that drive, and its *sustained* rate comes out to > about 69Mbyte/second. Sure, it'll take bursts at screaming-fast rates, > because, like the Linux kernel, it has a whacking great write-behind buffer. > Try specifying a filename of "/dev/null", which will bypass your disk > subsystem entirely, and give you some idea of what you can sustain in the > absence of actual disk-subsystem writes. _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
