15%
04.11.2011
desktop
06 7 desktop
07 8 desktop
08 10 desktop
09 9 desktop
10 1 serverer
11 2 serverer
12 3 serverer
13 4 serverer
The command processes the numbers from 1 to 10 inclusive, running as many jobs on each
15%
18.07.2013
-generation SSD, being tested on a 3Gbps SATA 2 bus.
I have an 80GB Intel 320 SSD, performing remarkably close to its specified sequential read rating of 270MBps [1], but it is the second-generation drive
15%
09.04.2019
unexplained delays of a few seconds while renaming some gigabyte-sized files [2] on a fast cloud instance [3]. I was able to reproduce his result in an AWS EC2 m5d.large instance running Ubuntu Server 18
15%
30.01.2024
256GB DDR4 ECC PC4-19200 2,400MHz
Storage
4x3.5-inch drive bays, slimline optical drive, LSI SAS 3008 12Gbps SAS (6Gbps SATA)
Networking
Intel I217 and I210 Gigabit Ethernet
14%
11.06.2014
architecture => 'i686'
10 kernel => 'Linux'
11 kernelrelease => '3.11.0-15-generic'
12 }
13 $hostname = 'sugar'
14 $operating_system = 'Ubuntu'
15 $operatingsystem = 'Ubuntu'
16 $operating
14%
02.02.2021
the slices, the higher the precision. You just need to throw CPUs at the problem: in this case, 5 million loops to reach 48 decimal places of accuracy.
Figure 1
14%
01.08.2019
.
Figure 3: Installing Python v3.6 for compatibility with Docker Scan.
For example, the command
$ python --version
Python 2.7.12
reports that Python v2 is installed. After installing the relevant
14%
25.03.2020
8 2 488383488 sda2
12 8 16 6836191232 sdb
13 8 64 6836191232 sde
14 8 80 39078144 sdf
15 8 48 6836191232 sdd
16 8 32 6836191232 sdc
17 11
14%
16.03.2021
=libaio, iodepth=32
fio-3.12
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=1420KiB/s][w=355 IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=3377: Sat Jan 9 15:31:04 2021
write: IOPS=352, BW=1410Ki
14%
28.11.2023
.json files (Listings 1 and 2) [2] to launch a Monitoror stack and supply its configuration, respectively.
Listing 1
monitoror_stack.yml
01 version: '3.5'
02 services:
03 monitoror:
04
