19%
21.08.2014
/origin/HEAD -> origin/master
09 remotes/origin/android-goldfish-2.6.29
10 remotes/origin/android-goldfish-3.4
11 remotes/origin/linux-goldfish-3.0-wip
12 remotes/origin/master
13 [...]
14 [root@pc]# git checkout
19%
30.11.2020
cri-o-${CRIO_VERSION}
The following NEW packages will be installed
cri-o-1.17
0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade.
Need to get 17.3 MB of archives.
After this operation
19%
30.01.2020
| 12724500| 46.7333| 3.6727e-06| 3.09%| d = 0.0
155| 50898000| 195.426| 3.83956e-06| 12.94%| for k in range(0, d_num):
156| 38173500| 165.494| 4.33531e
19%
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
19%
14.11.2013
A study [3] of real memory errors took place at Google. During their investigations they found that one third of the machines and more than eight percent of the DIMMs saw correctable errors per year
19%
13.02.2017
will be followed this time, although test builds are now available online [2].
Jigsawing
One core feature of Java 9 par excellence is the Java Platform Module System that became known as Project Jigsaw [3]. Thus
19%
14.08.2017
:31 FS_scan.csv
$ gzip -9 FS_scan.csv
$ ls -lsah FS_scan.csv.gz
268K -rw-r--r-- 1 laytonjb laytonjb 261K 2014-06-09 20:31 FS_scan.csv.gz
The original file is 3.2MB, but after using gzip with the -9
19%
30.11.2020
: Pull complete
3db6272dcbfa: Pull complete
Digest: sha256:8be26f81ffea54106bae012c6f349df70f4d5e7e2ec01b143c46e2c03b9e551d
Status: Downloaded newer image for registry:2
docker.io/library/registry:2
19%
05.12.2016
, followed in September by Apricity OS 09.2016 [1] (code-named Aspen), which was used for this test. The project was based on Gnome only in its beta phase, although another GTK desktop, Cinnamon, was added
19%
14.03.2018
.
Figure 3: After the fix, CPU utilization dropped from 1,200 to 200 percent.
The average response time of the read nodes decreased from 3ms to about 0.15ms. The CPU utilization of the database dropped
