22%
11.02.2016
.40 <- < 71% idle >
0 1.00 0.00 0.37 0.00 0.00 0.06 0.00 0.00 0.00 98.57
1 100.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
2 3.77 0.00
22%
13.12.2022
Packages:
(1/6): dhcp-common-4.3.6-47.el8.noarch.rpm 902 kB/s | 206 kB 00:00
(2/6): dhcp-libs-4.3.6-47.el8.x86_64.rpm 3.1 MB/s | 147 kB 00:00
(3
22%
29.09.2020
-amd64.tar.gz.sha256sum
[...snip]
e6be589df85076108c33e12e60cfb85dcd82c5d756a6f6ebc8de0ee505c9fd4c helm-v3.1.2-linux-amd64.tar.gz
$ sha256sum helm-v3.1.2-linux-amd64.tar.gz
e6be589df85076108c33e12e60cfb85
21%
05.08.2024
= [size][size]int {{0},{0},}
08
09 for i := 0; i < size; i++ {
10 for j := 0; j < size; j++ {
11 array[i][j]++
12 }
13 }
14
15
21%
17.02.2015
Galileo
Yocto Linux, VxWorks (RTOS), Windows
Intel Quark X1000
Single 32-bit Intel Pentium (x86) @400MHz
Integrated Intel GPU
256 MB DDR3, 512KB embedded SRAM, 8
21%
11.04.2016
(512 MB) copied, 49.1424 s, 10.4 MB/s
If you want to empty the read and write cache for benchmark purposes, you can do so using:
sync; echo 3 > /proc/sys/vm/drop_caches
Sequential access
21%
07.10.2014
(Listing 3).
Listing 3
Defining Replication Factors
01 # dog vdi list
02 Name Id Size Used Shared Creation time VDI id Copies Tag
03 one.img 0 4.0 MB 0.0 MB 0.0
20%
02.08.2021
the configuration and capabilities of memory DIMMs and revealed that my system has four DDR3 RAM devices of 2048MB configured at speeds of 1333MTps (mega transfers per second).
Playing with RAM Drives
To begin, you
20%
30.01.2020
and a truncated distance
243| 12475000| 50.5158| 4.04936e-06| 3.04%| d = 0.0
244| 49900000| 209.465| 4.1977e-06| 12.60%| for k in range(0, d_num):
245
20%
09.12.2019
| 12475000| 50.5158| 4.04936e-06| 3.04%| d = 0.0
244| 49900000| 209.465| 4.1977e-06| 12.60%| for k in range(0, d_num):
245| 37425000| 175.823| 4.69801e-06
