It'll be under /usr/local/lib{64}/uhd/examples
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.
On 2015-05-07 15:32, Murphy, John wrote:
> The sequential rates I gave are the published rates for the SSD. Maybe
> (probably?) specsmanship, sure.
> But since it does mostly keep up, isn't this a case of just needing
> the correct buffer set-up to allow it to ride through the worst of the
> hiccups?
>
> I am going to have to find and figure out how to run
> rx_samples_to_file before I can let you know if it makes any
> difference.
>
> - John
>
> On Thu, May 7, 2015 at 3:07 PM, <[email protected]> wrote:
>
>> How did you test your sequential-write rate?
>
>> Writing files that are less than the current write-behind buffer size in the
>> kernel will give you a very false sense of how fast your disk subsystem is.
>
>> Again, if you use rx_samples_to_file, instead of GR at all, do you see any
>> significant change in the overrun issues?
>
> _______________________________________________
> Discuss-gnuradio mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio [1]
Links:
------
[1] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
