21%
31.10.2025
(depending on the RAID level). These chunks are usually 1GB for data and 256MB for metadata. One exception is the first metadata chunk, which mkfs.btrfs creates 1GB in size, assuming there is enough space
21%
25.03.2021
, 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
20%
07.11.2023
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
20%
29.09.2020
sitting at less than 50MB (and using less than half the RAM of a standard cluster) the binary that runs K3s is a sight to behold and well worth getting your hands on. Especially when it's deemed production
20%
13.12.2018
(USB 2), and a Samsung Fit Plus 32 (USB 3).
Disk Caches
The OS is not the only player in the caching business. Examining a Samsung 750 SATA SSD drive, you cannot but notice a 256MB RAM buffer [8
20%
17.02.2015
Galileo
Yocto Linux, VxWorks (RTOS), Windows
Intel Quark X1000
Single 32-bit Intel Pentium (x86) @400MHz
Integrated Intel GPU
256 MB DDR3, 512KB embedded SRAM, 8
19%
03.04.2024
on machines with only one CPU core and 512MB of RAM; the minimalist K3s setup itself only uses 250MB. As one of the radical cost-cutting measures, K3s dispenses with the I/O-intensive etcd database
19%
21.01.2021
.86–2.66GHz
Jan 2010
Nehalem
Dual-core; 32+32 L1, 256KB L2, 3MB L3; 2.8GHz, two threads per core
Table 2: Supercomputer Processor Progression
Date
Processor
19%
11.05.2021
sizes (Listing 1). The second script (Listing 2) is the same as Listing 1, but uses double precision.
Listing 1: Single-Precision Square Matrix Multiply
# Example SGEMM
for N = [2, 4, 8, 16, 32, 64, 128, 256
19%
12.09.2013
, integrated
AMD Radeon HD 6320, integrated
Integrated/SoC
Graphics memory
Up to 512MB
128MB
256MB
384MB
256MB
RAM
1GB
1GB
2GB
