30%
30.07.2019
News, “The data breach that occurred on March 22nd and 23rd this year allowed attackers to steal information of customers who had applied for a credit card between 2005 and 2019.”
Capital One had
30%
12.03.2013
_nor/s rMB_dir/s wMB_dir/s rMB_svr/s wMB_svr/s ops/s rops/s wops/s
192.168.1.250:/home
1230649.19 1843536.81 0.00 0.00 1229407.77 1843781
30%
11.04.2016
(512 MB) copied, 49.1424 s, 10.4 MB/s
If you want to empty the read and write cache for benchmark purposes, you can do so using:
sync; echo 3 > /proc/sys/vm/drop_caches
Sequential access
30%
12.05.2021
Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 077 063 --- Pre-fail Always - 56770409
3 Spin
30%
21.08.2012
-14.el6_3.x86_64.rpm | 2.2 MB 00:01
(3/4): php-common-5.3.3-14.el6_3.x86_64.rpm | 522 kB 00:00
(4/4): php-gd-5.3.3-14.el6_3.x86_64.rpm
29%
20.10.2013
: Z1F35P0G
LU WWN Device Id: 5 000c50 050b954c3
Firmware Version: CC27
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl
29%
27.08.2014
record size, (2) sequential read testing with 1MB record size, and (3) random write and read (4KB). In running these tests, I wanted to see what block layer information ioprof revealed.
The system I
29%
30.01.2024
Dell Precision Workstation T7910
Power
1,300W
CPU
2x Intel Xeon Gold E5-2699 V4, 22 cores, 2.4GHz, 55MB of cache, LGA 2011-3
GPU, NPU
n/a*
Memory
29%
04.08.2020
(minified by 25.99X)
from python:2.7-alpine - 84.3MB => 23.1MB (minified by 3.65X)
from python:2.7.15 - 916MB => 27.5MB (minified by 33.29X)
from centos:7 - 647MB => 23MB (minified by 28.57X)
from centos
29%
21.01.2021
May 1988
AMD K6-2
MMX and 3DNOW! SIMD, 200–570MHz; 64KiB L1 cache
Jun 1998
Pentium II Xeon
SIMD; L2 cache from 512KB to 2MB
Feb 1999
Pentium III
9
