12%
11.04.2016
network adapters, one for administration and one for the web server. I gave the system 1GB memory, but it has not yet used more than 200MB.
Then, boot the image. You have several choices:
Add
12%
27.08.2014
record size, (2) sequential read testing with 1MB record size, and (3) random write and read (4KB). In running these tests, I wanted to see what block layer information ioprof revealed.
The system I
12%
04.08.2020
='GET /'
docker-slim[build]: info=http.probe.call status=200 method=GET target=http://172.17.0.3:80/ attempt=1 time=2020-11-11T12:52:01Z
docker-slim[build]: info=http.probe.summary total=1 failures=0 successful=1
12%
03.02.2022
,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25,57
26,58
27,59
28,60
29,61
30,62
31,63
The lstopo tool
12%
14.09.2021
$(find /sys/devices/system/cpu -regex ".*cpu[0-9]+/topology/thread_siblings_list") | sort -n | uniq
0,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25
12%
28.11.2023
.service]]
45 id = "ping"
46 label = "PING"
47 [[probe.service.node]]
48 id = "invalidiping"
49 label = "Invalid IP Ping"
50 mode = "poll"
51 replicas = ["icmp://129.0.0.1"]
52
53 [[probe.service]]
54 id = "port
12%
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
12%
12.09.2013
see that the base module is by far the largest, weighing in at more than 200KB.
When a module is loaded, it is copied to /etc/selinux/targeted/modules/active/modules/. When the system is rebooted
12%
25.03.2021
.00 MiB 2144.34 MB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Sat Jan 9 16:36:21 2021
State : clean, resyncing
12%
07.06.2019
_web latest c100b674c0b5 13 months ago 19MB
nginx alpine bf85f2b6bf52 13 months ago 15.5MB
With the image ID in hand, you can inspect the image manifest:
docker inspect bf85f2b6bf52
