100%
01.06.2024
Rubén Llorente ... : [devuan]
10 donkey:
11 user: root
12 host: donkey.operationalsecurity.es
13 tags: [devuan]
14 zebra:
15 user: root
16 host: zebra.operationalsecurity.es
17 tags: [devuan]
18
19
29%
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
27%
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
26%
12.05.2020
signatures
2020/05/02 07:47:53 info unpack layer: sha256:7ddbc47eeb70dc7f08e410a6667948b87ff3883024eb41478b44ef9a81bf400c
2020/05/02 07:47:54 info unpack layer: sha256:c1bbdc448b7263673926b8fe2e88491e5083a8b4b06
25%
04.12.2013
(2,400 bytes/0.000021 sec). This throughput is fairly respectable for this case, but it definitely includes cache effects.
Now I’ll try 256 iterations and see what happens to the I/O in the strace
24%
30.11.2025
creates a 256MB file in the current directory along with process for the job. This process reads complete file content in random order. Fio records the areas that have already been read and reads each area
24%
11.02.2016
defaults for Table Definition Cache, from 256 to 400, would be sufficiently dimensioned for this example.
Query Cache
The next relevant MySQL parameter from the SQL area is the Query Cache. This should
23%
18.12.2013
(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
22%
26.02.2014
total packets: sent: 12,243,355 recv: 1,467,914
bytes sent: total: 16.90 G per-sec: 3.22 M/s
bytes recv: total: 114.04 M
22%
02.08.2021
- 400
10 Spin_Retry_Count 0x0013 100 099 --- Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 --- Old_age Always - 135
184 End
