22%
05.08.2024
= [size][size]int {{0},{0},}
08
09 for i := 0; i < size; i++ {
10 for j := 0; j < size; j++ {
11 array[i][j]++
12 }
13 }
14
15
22%
28.11.2021
can use to test security vulnerabilities, enumerate networks, execute attacks, and evade detection" [1], has been written up in a number of books. Linux Magazine
reported more than 12 years ago [2
22%
30.01.2020
: 1 (f=1): [w(1)][100.0%][r=0KiB/s,w=1401KiB/s][r=0,w=350 IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=3104: Sat Oct 12 14:39:08 2019
write: IOPS=352, BW=1410KiB/s (1444kB/s)(82.8Mi
22%
20.02.2012
.57, 0.00, 12.76, 85, 0
2012-01-09 21:09:21, 84, 4.84, 0, 0.29, 17.36, 0.00, 5.09, 90, 0
2012-01-09 21:09:47, 80, 4
22%
19.11.2019
Jobs: 1 (f=1): [w(1)][100.0%][w=654MiB/s][w=167k IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=1225: Sat Oct 12 19:20:18 2019
write: IOPS=168k, BW=655MiB/s (687MB/s)(10.0GiB/15634msec); 0
21%
12.09.2013
');
burncpu
-----------------
00:00:30.000053
The results take 30 seconds to deliver. The CPU load table shows the associated database process for this time (Figure 1).
Listing 1
burncpu
01
21%
22.05.2012
:
Scientific Linux 6.2
2.6.32-220.4.1.el6.x86_64 kernel
GigaByte MAA78GM-US2H motherboard
AMD Phenom II X4 920 CPU (four cores)
8GB of memory (DDR2-800)
The OS and boot drive are on an IBM DTLA
21%
21.08.2012
just two nodes: test1, which is the master node, and n0001, which is the first compute node):
[laytonjb@test1 ~]$ pdsh -w test1,n0001 uptime
test1: 18:57:17 up 2:40, 5 users, load average: 0.00, 0.00
21%
07.10.2014
by the process
12m
12MB
S
Status of process
R
S
= sleeping, R
= running, Z
= zombie
%CPU
Percent CPU being used by the process on a per-CPU basis
21%
03.08.2023
in 2014. At the time of writing, the available Kea versions were 2.2.0 (July 2022, Current-Stable) and 2.3.6 (March 2023, Experimental-Development). Most distributions have prebuilt Kea packages
