13%
07.01.2014
.
The approach used by Rubel has several advantages. The first is that the most recent backup, backup.0
, always contains the full backup and backup.1
through backup.
<
N
>, where <N> is the last incremental
13%
19.11.2019
Jobs: 1 (f=1): [w(1)][100.0%][w=654MiB/s][w=167k IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=1225: Sat Oct 12 19:20:18 2019
write: IOPS=168k, BW=655MiB/s (687MB/s)(10.0GiB/15634msec); 0
13%
20.03.2014
(hercules) 03.12.2013 _x86_64_ (2 CPU)
09:46:03 runq-sz plist-sz ldavg-1 ldavg-5 ldavg-15 blocked
09:46:13 1 468 0.02 0.06 0.14 0
9
13%
26.02.2014
reqs merged: 3.76/s Write reqs completed: 2.12/s
Read BW: 0.01 MB/s Write BW: 0.02 MB/s
Avg sector size issued 25.28 Avg
12%
05.08.2024
run("row")
09 }
10 }
11
12 func BenchmarkColumn(b *testing.B) {
13 //b.ResetTimer()
14 for i := 0; i < b.N; i++ {
15 run("column")
16 }
17 }
Figure 5 shows
12%
20.05.2014
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
12%
07.10.2014
/lib/sheepdog
root 582 581 0 13:13 ? 12:00:00 AM sheep -p 7000 /var/lib/sheepdog
# grep sheep /proc/mounts
/dev/sdb1 /var/lib/sheepdog ext4 rw,relatime,data=ordered 0 0
# grep sheep /etc/fstab
/dev
12%
20.02.2012
time: 11.79 secs
Data transferred: 2.47 MB
Response time: 0.22 secs
Transaction rate: 35.79 trans/sec
Throughput: 0
12%
11.10.2016
log. The storage is clearly divided: The kernel has tagged 0x0000000100000000
to 0x00000004ffffffff
(4-20GiB) as persistent (type 12)
. The /dev/pmem0
device shows up after loading the driver. Now
12%
22.09.2016
log. The storage is clearly divided: The kernel has tagged 0x0000000100000000
to 0x00000004ffffffff
(4-20GiB) as persistent (type 12)
. The /dev/pmem0
device shows up after loading the driver. Now
