18%
10.06.2024
.
One comment made on the announced list is that Aurora submitted a result that finished third, but only 40% of the system was used. The expectation is that once Aurora is fully up and running, the entire
18%
30.11.2020
.
A fleet of 8TB SSDs, for example, costs around $1,200 (EUR2,000) on the free market. The price can undoubtedly be reduced considerably if you buy 30 or 40 units from your trusted hardware dealer. In any
18%
30.11.2020
.0 # Left endpoint
36 b=2.0 # Right endpoint
37 n=1024 # Number of trapezoids
38 dest=0 # Destination for messages (rank 0 process)
39 total=-1.0 # Initialize to negative number
40
41 h
18%
28.11.2021
}
39
40 result := hex.EncodeToString(h.Sum(nil))
41
42 return result
43 }
The genChecksum() function takes two parameters. The first is the path to the file whose checksum is to be calculated
18%
28.11.2021
_configs:
37 - targets:
38 - "http://target_server" # Target to probe with http.
39 relabel_configs:
40 - source_labels: [__address__]
41 target_label: __param_target
42
18%
21.08.2014
/fs/proc/meminfo.c 2014-03-31 05:40:15.000000000 +0200
+++ new/fs/proc/meminfo.c 2014-05-11 16:33:19.148771809 +0200
@@ -131,7 +131,7 @@
"Committed_AS: %8lu kB\n"
"VmallocTotal: %8lu kB\n"
"VmallocUsed: %8lu
18%
21.08.2014
bandwidths are shown in Table 1. However, the predefined values lead to a 40Gb and a 100Gb connection having the same spanning tree cost as a port channel comprising two 10Gb connections, in which the cost
18%
07.10.2014
_create_data( PROC_FILE_NAME, S_IRUGO, NULL, &prochello_fops, NULL);
33 if (!proc_file)
34 return -ENOMEM;
35 return 0;
36 }
37
38 static void __exit prochello_exit(void)
39 {
40 if( proc_file )
41
18%
02.08.2022
, but for the sake of argument, I will limit the time to 30-40 seconds per benchmark.
Running all the NBP benchmarks would take too much time. Eight benchmarks at 30 seconds each is four minutes. I'm not sure how
18%
02.02.2021
100TB of user data, almost 40TB of parity data is required, whereas 300TB of disk space would be needed for classic full replication.
On the other side of the coin, when resynchronization becomes
