30%
11.04.2016
B/s ( 2.2 Gbit/s)
128 KiB blocks: 2176.5 IO/s, 272.1 MiB/s ( 2.3 Gbit/s)
256 KiB blocks: 751.2 IO/s, 187.8 MiB/s ( 1.6 Gbit/s)
512 KiB blocks: 448.7 IO/s, 224.3 MiB/s ( 1.9 Gbit/s)
1 MiB blocks
30%
21.08.2012
: 18:59:43 up 2:42, 5 users, load average: 0.05, 0.02, 0.01
n0001: ssh: connect to host n0001 port 22: Connection timed out
pdsh@test1: n0001: ssh exited with exit code 255
You can do many other
30%
15.02.2012
call count for the MB range intervals. Figure 6 plots the write IO function call count for the GB range intervals. Figure 7 plots the write IO function call count for the TB range intervals
30%
26.01.2012
call count for the MB range intervals. Figure 6 plots the write IO function call count for the GB range intervals. Figure 7 plots the write IO function call count for the TB range intervals
29%
05.09.2011
can see how the arp cache poisoning works:
$ sudo nemesis arp -v -r -d eth0 -S 192.168.1.2 \
-D 192.168.1.133 -h 00:22:6E:71:04:BB -m 00:0C:29:B2:78:9E \
-H 00:22:6E:71:04:BB -M 00:0C:29:B2:78:9E
29%
20.06.2012
/shm
10.1.0.250:/var/chroots/sl6.2
53G 29G 22G 57% /vnfs
10.1.0.250:/home 53G 29G 22G 57% /home
10.1.0.250:/opt 53G 29G 22G 57% /opt
10.1.0.250:/usr
29%
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
29%
20.02.2012
time: 11.79 secs
Data transferred: 2.47 MB
Response time: 0.22 secs
Transaction rate: 35.79 trans/sec
Throughput: 0
29%
12.05.2020
68e152db7e5bb36b1cca638",
"sha256:37b9a4b2218692d028f9f26aa9cb85bf1f56d9abe612ba31304643bdb448484f",
"sha256:b16af11cbf2977eb52ba4d6cee5b713721cc19812b8c90ea1f22e7e
29%
05.08.2024
are just that, benchmarks. Listing 6 introduces the testing framework, the loop variable N allowing for repeated testing and the ResetTimer() annotation a useful reminder to exclude test setup overheads
