23%
29.09.2020
(abridged)
$ docker build -t dockly .
Sending build context to Docker daemon 16.52MB
Step 1/9 : FROM node:8-alpine
8-alpine: Pulling from library/node
e6b0cf9c0882: Pull complete
93f9cf0467ca: Pull
23%
02.08.2021
with a different size (Listing 3). The output from the second command verifies that the RAM drives were created.
Listing 3
Adding RAM Drive of 32MB
$ sudo rapiddisk -a 32
rapiddisk 7.2.0
Copyright
22%
15.02.2012
2
0
0
0
0
0
2
256KB < < 512KB
2
2
2
3
2
2
2
3
512KB < < 1MB
3
2
2
22%
26.01.2012
2
0
0
0
0
0
2
256KB < < 512KB
2
2
2
3
2
2
2
3
512KB < < 1MB
3
2
2
22%
07.02.2019
exiting the data region, the data from the accelerator is copied back to the host. Table 3 shows a simple example of using the copy
clause.
Table 3: The copy
Clause
Fortran
C
!$acc data copy(a
22%
11.04.2016
.5 MiB/s ( 79.7 Mbit/s)
256 KiB blocks: 53.9 IO/s, 13.5 MiB/s (113.1 Mbit/s)
512 KiB blocks: 39.8 IO/s, 19.9 MiB/s (166.9 Mbit/s)
1 MiB blocks: 33.3 IO/s, 33.3 MiB/s (279.0 Mbit/s)
2 Mi
22%
04.08.2020
-slim[build]: info=image id=sha256:231d40e811cd970168fb0c4770f2161aa30b9ba6fe8e68527504df69643aa145 size.bytes=126323486 size.human=126 MB
docker-slim[build]: info=image.stack index=0 name='nginx:latest' id='sha256
22%
09.12.2021
of threads, use:
$ plzip -v -9 -n 32 package-list.txt
package-list.txt: 2.640:1, 37.88% ratio, 62.12% saved, 11626 in, 4404 out.
The -n 32
option tells plzip
to use 32 threads to perform the compression
22%
21.01.2020
RAID
$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sde1[4] sdd1[3] sdc1[2] sdb1[1] nvme0n1p1[0](J)
20508171264
22%
30.01.2020
Conversion
$ sudo lvs -a vg-cache -o devices,segtype,lvattr,name,vgname,origin
Devices Type Attr LV VG Origin
/dev/nvme0n1(0) linear Cwi-aoC--- [fast
