Search

, ioengine=libaio, iodepth=32 fio-3.12 Starting 1 process Jobs: 1 (f=1) test: (groupid=0, jobs=1): err= 0: pid=5956: Sat Jan 9 16:38:53 2021 read: IOPS=256k, BW=998MiB/s (1047MB/s)(2045MiB/2049msec

of the inodes when the filesystem is created, resulting in a fixed number of inodes. For example, ext3 and ext4 filesystems do this. The result is that the filesystem has a fixed number of inodes, which

Viewing Server Topology 01 # numactl --hardware available: 8 nodes (0-7) node 0 cpus: 0 1 2 3 4 5 6 7 8 9 node 0 size: 16373 MB node 0 free: 15837 MB node 1 cpus: 10 11 12 13 14 15 16 17 18 19 node 1

                5.3M  8.2k  5.3M   1% /run/lock /dev/nvme1n1p1       1.1T  488G  468G  52% /home /dev/nvme0n1p1       536M  6.4M  530M   2% /boot/efi /dev/sda1            6.0T  3.4T  2.4T  60% /home2 tmpfs

Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 64 bytes from 52.90.56.122: icmp_seq=3 ttl=48 time=40.492 ms [ output truncated ] Welcome to Ubuntu 20.04.1 LTS

ZJOUoUsZGlkk client2:q0eL78zFrbnESW6c/F0qit5MNCpS8IBgyh1BdXiyyuI client3:zkq8eT31Nib3IHWfp0yyu15BCW52VMbY8+LhVUt3ylA The client uses the appropriate password in the /etc/stunnel/psk-client1.txt file: client1:Wf

buffered disk reads: 616 MB in 3.00 seconds = 205.03 MB/sec $ hdparm -T /dev/sda /dev/sda: Timing cached reads: 6292 MB in 2.00 seconds = 3153.09 MB/sec If this were a spinning disk, you would also

754 pages of about 63MB) with details on where to find the latest release. In my case, this was version 19.11.480. The docs are also now public, which is more convenient (an access token attached

(One-by-One) 1 #include 2 3 /* Our structure */ 4 struct rec 5 { 6 int x,y,z; 7 float value; 8 }; 9 10 int main() 11 { 12 int counter; 13 struct rec my_record; 14 int counter_limit; 15

and 47.52% in the US, according to data provided by the Can I Use website [4]. Even on those Linux systems that can fully support TLS 1.3, the prior version should remain enabled for the time being ... After a decade in service, TLS 1.2 is showing many signs of aging. Its immediate successor, TLS 1.3, has earned the approval of the IETF. Some major changes are on the way. ... TLS 1.3 ... TLS 1.3 and the return of common sense