Displaying 3 results from an estimated 3 matches for "read_rat".
Did you mean:
read_at
2019 Jun 07
1
Problem with opusfile & ndk
Hi Xiph.org Team.
We are using opusfile library <https://github.com/xiph/opusfile> for
streaming *.opus* audio in our projects.
But now we have a problem with building opusfile library for android with
*ndk-build*.
In particular, with arm64-v8a platform: Google removed <sys/timeb.h> from
android.
And now building opusfile with nkd-build crashes with error "fatal error:
2019 Nov 30
0
Re: [PATCH nbdkit 2/3] filters: stats: Measure time per operation
...can, but showing system throughput require more thinking.
We have 3 uses cases. Here is a possible way to show both system throughput
and fine grain per operation stats.
I'm assuming that for system throughput we like to think about the
total bytes processed
by the system in each direction:
read_rate = pread_bytes / total_time
write_rate = (pwrite_bytes + zero_bytes + trim_bytes) / total_time
1. copy image to nbdkit
total: 2300 ops, 6 GiB, 2.150 s, 2925.71 wMiB/s
write: 1271 ops, 1.14 GiB, 0.398 s, 2922.22 MiB/s
zero: 1027 ops, 4.86 GiB, 0.012 s, 414723.03 MiB/s
extents: 1 ops, 2.00 GiB, 0.0...
2019 Nov 30
2
Re: [PATCH nbdkit 2/3] filters: stats: Measure time per operation
On Sat, Nov 30, 2019 at 02:17:06AM +0200, Nir Soffer wrote:
> Previously we measured the total time and used it to calculate the rate
> of different operations. This is incorrect and hides the real
> throughput. A more useful way is to measure the time we spent in each
> operation.
>
> Here is an example run with this change:
>
> $ ./nbdkit --foreground \
> --unix