16%
30.11.2025
62
787
10MB < < 100MB
0
0
0
0
0
0
0
2
Table 4 from the MPI strace Analyzer report; all-zero rows for sizes >100MB
16%
16.10.2012
bytes:215392635 (215.3 MB) TX bytes:1759757 (1.7 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK
16%
11.04.2016
/s wMB/s avgrq-sz ...
sdb 0.00 28.00 1.00 259.00 0.00 119.29 939.69 ...
Parallelism
Multiple computers can access enterprise storage, and multiple threads can access
16%
11.02.2016
329792 0 137352 1252 137488 880 3506 5 2 22 71 0 <- < Severe swapping >
0 10 597776 117244 320 317840 0 29400 588 29400 664 2522 2 2 0 96 0 <- < Process killed >
0 13 1667548
16%
11.04.2016
Network Configuration (2)
[Match]
Name=docker0
[Network]
DNS=192.168.100.1
Address=192.168.100.42/24
Gateway=192.168.100.1
Before the bridge device can be configured, you first need to make sure
16%
13.06.2016
]
Name=docker0
[Network]
DNS=192.168.100.1
Address=192.168.100.42/24
Gateway=192.168.100.1
Listing 3
Network Configuration (2)
[Match]
Name=enp2s25
[Network]
Bridge=docker0
16%
30.11.2025
1
1
0
Backup
50
1
1
1
Network printer
100
1
0
0
File server
50
1
1
0
15%
05.08.2024
spans 100 million elements, taking up 800MB of RAM – not at all an unusual size in any kind of numerical computing. This system is equipped with 8GB of RAM, so allocating the array itself is no trouble
15%
11.04.2016
:* LISTEN 4766/hiawatha
tcp 0 0 127.0.0.1:10000 0.0.0.0:* LISTEN 944/perl
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 676/sshd
15%
07.01.2024
M 74M 0 100% /snap/core22/864
/dev/loop15 squashfs 12.4M 12.4M 0 100% /snap/snap-store/959
/dev/loop16 squashfs 73.9M 73.9M 0 100% /snap/core22/817
/dev/loop17 squashfs 349.8M 349
