Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- tinymembench v0.4.9 (simple benchmark for memory throughput and latency)
- ==========================================================================
- == Memory bandwidth tests ==
- == ==
- == Note 1: 1MB = 1000000 bytes ==
- == Note 2: Results for 'copy' tests show how many bytes can be ==
- == copied per second (adding together read and writen ==
- == bytes would have provided twice higher numbers) ==
- == Note 3: 2-pass copy means that we are using a small temporary buffer ==
- == to first fetch data into it, and only then write it to the ==
- == destination (source -> L1 cache, L1 cache -> destination) ==
- == Note 4: If sample standard deviation exceeds 0.1%, it is shown in ==
- == brackets ==
- ==========================================================================
- C copy backwards : 121.9 MB/s
- C copy backwards (32 byte blocks) : 121.8 MB/s
- C copy backwards (64 byte blocks) : 121.8 MB/s
- C copy : 121.8 MB/s
- C copy prefetched (32 bytes step) : 120.7 MB/s (0.3%)
- C copy prefetched (64 bytes step) : 121.8 MB/s
- C 2-pass copy : 112.6 MB/s
- C 2-pass copy prefetched (32 bytes step) : 111.6 MB/s
- C 2-pass copy prefetched (64 bytes step) : 112.6 MB/s
- C fill : 227.5 MB/s (0.3%)
- C fill (shuffle within 16 byte blocks) : 227.5 MB/s
- C fill (shuffle within 32 byte blocks) : 227.5 MB/s (0.3%)
- C fill (shuffle within 64 byte blocks) : 227.4 MB/s
- ---
- standard memcpy : 117.2 MB/s
- standard memset : 227.3 MB/s
- ==========================================================================
- == Memory latency test ==
- == ==
- == Average time is measured for random memory accesses in the buffers ==
- == of different sizes. The larger is the buffer, the more significant ==
- == are relative contributions of TLB, L1/L2 cache misses and SDRAM ==
- == accesses. For extremely large buffer sizes we are expecting to see ==
- == page table walk with several requests to SDRAM for almost every ==
- == memory access (though 64MiB is not nearly large enough to experience ==
- == this effect to its fullest). ==
- == ==
- == Note 1: All the numbers are representing extra time, which needs to ==
- == be added to L1 cache latency. The cycle timings for L1 cache ==
- == latency can be usually found in the processor documentation. ==
- == Note 2: Dual random read means that we are simultaneously performing ==
- == two independent memory accesses at a time. In the case if ==
- == the memory subsystem can't handle multiple outstanding ==
- == requests, dual random read has the same timings as two ==
- == single reads performed one after another. ==
- ==========================================================================
- block size : single random read / dual random read
- 1024 : 0.0 ns / 0.0 ns
- 2048 : 0.0 ns / 0.1 ns
- 4096 : 0.0 ns / 0.0 ns
- 8192 : 0.0 ns / 0.0 ns
- 16384 : 0.0 ns / 0.0 ns
- 32768 : 0.2 ns / 0.2 ns
- 65536 : 19.4 ns / 38.6 ns
- 131072 : 29.0 ns / 57.9 ns
- 262144 : 38.2 ns / 78.4 ns
- 524288 : 42.8 ns / 89.1 ns
- 1048576 : 55.0 ns / 111.8 ns
- 2097152 : 179.5 ns / 359.5 ns
- 4194304 : 246.0 ns / 492.1 ns
- 8388608 : 284.8 ns / 569.4 ns
- 16777216 : 313.3 ns / 626.9 ns
- 33554432 : 335.4 ns / 670.9 ns
- 67108864 : 359.5 ns / 718.9 ns
Add Comment
Please, Sign In to add comment