18%
12.05.2021
30.85 72.31 13.16 20.40 0.26 70.44 83.89 1.97 3.52
nvme0n1 58.80 12.22 17720.47 48.71 230.91 0.01 79.70 0.08 0.42 0.03 0.00 301.34 3
18%
01.06.2024
is 20x because only 95 percent of the algorithm can execute in parallel (compute the fraction 1/20 from that 5% number). That limitation led to a search for embarrassingly parallel
algorithms
18%
30.01.2020
.0.0.0/0
45 - IpProtocol: udp
46 FromPort: 0
47 ToPort: 65535
48 CidrIp: 0.0.0.0/0
49 VpcId:
50 Ref: FortiVPC
51
52 InstanceProfile:
53 Properties:
54
18%
11.10.2016
_list = [];
47 for x in range(140): # hard coded as an example
48 cpu_percent_local = [];
49 epoch_list.append(time.time());
50
51 cpu
18%
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
18%
14.08.2017
": "Contact id = #{@contact.id} deleted." }
45 else
46 @response_message = { "message": "Contact id = #{@contact.id} not found." }
47 end
48 json @response_message
49 end
50
51 options '/' do
52
18%
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
18%
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
18%
02.02.2021
't be parallelized, you can tell up front, without knowing any other details about the problem, that the maximum speedup theoretically possible is 20x (Equation 3
17%
22.12.2017
For nearly 20 years, web servers have relied on Gzip compression to compress HTML, CSS, and miscellaneous text files, which the browser then receives and unpacks again, speeding up data transfer
