Embed Size (px)
Citation preview
Filesystem Aging:It’s More Usage than Fullness
Alex Conway, Eric Knorr, Yizheng Jiao, Michael A. Bender, William Jannen, Rob Johnson, Donald Porter, and Martin Farach-Colton
What is filesystem aging?
Aging is fragmentation over time
What is filesystem aging?
Aging is fragmentation over time
What is filesystem aging?
Aging is fragmentation over time
Performance
File
Sys
tem
Spe
ed
Time
Is aging a problem?
Is aging a problem?
Chris Hoffman at howtogeek.com says:
“Linux’s ext2, ext3, and ext4 file systems… [are] designed to avoid fragmentation in normal use.”
“If you do have problems with fragmentation on Linux, you probably need a larger hard disk.”
Is aging a problem?
Chris Hoffman at howtogeek.com says:
“Linux’s ext2, ext3, and ext4 file systems… [are] designed to avoid fragmentation in normal use.”
“If you do have problems with fragmentation on Linux, you probably need a larger hard disk.”
“Modern Linux filesystems keep fragmentation at a minimum…Therefore it
is not necessary to worry about fragmentation in a Linux system.”
Is aging a problem?
Chris Hoffman at howtogeek.com says:
“Linux’s ext2, ext3, and ext4 file systems… [are] designed to avoid fragmentation in normal use.”
“If you do have problems with fragmentation on Linux, you probably need a larger hard disk.”
“Modern Linux filesystems keep fragmentation at a minimum…Therefore it
is not necessary to worry about fragmentation in a Linux system.”
Is aging a problem?
Aging is not a problem
(unless your disk is full)
Chris Hoffman at howtogeek.com says:
“Linux’s ext2, ext3, and ext4 file systems… [are] designed to avoid fragmentation in normal use.”
“If you do have problems with fragmentation on Linux, you probably need a larger hard disk.”
“Modern Linux filesystems keep fragmentation at a minimum…Therefore it
is not necessary to worry about fragmentation in a Linux system.”
Is aging a problem?
Aging is not a problem
(unless your disk is full)
Recent work: Aging is a problem!
Recent work on aging
Recent work on aging
“File Systems Fated for Senescence? Nonsense, says Science!” Conway et. al. FAST 2017
Recent work on aging
“File Systems Fated for Senescence? Nonsense, says Science!” Conway et. al. FAST 2017
On modern filesystems, aging is severe and happens quickly even if your disk is almost empty.
Recent work on aging
“File Systems Fated for Senescence? Nonsense, says Science!” Conway et. al. FAST 2017
“Geriatrix: Aging what you see and what you don’t see. A file system aging approach for modern storage systems” Kadekodi et. al. ATC 2018
On modern filesystems, aging is severe and happens quickly even if your disk is almost empty.
Recent work on aging
“File Systems Fated for Senescence? Nonsense, says Science!” Conway et. al. FAST 2017
“Geriatrix: Aging what you see and what you don’t see. A file system aging approach for modern storage systems” Kadekodi et. al. ATC 2018
On modern filesystems, aging is severe and happens quickly even if your disk is almost empty.
Real world file systems show a lot of aging, as well as free space fragmentation.
Recent work on aging
“File Systems Fated for Senescence? Nonsense, says Science!” Conway et. al. FAST 2017
“Geriatrix: Aging what you see and what you don’t see. A file system aging approach for modern storage systems” Kadekodi et. al. ATC 2018
On modern filesystems, aging is severe and happens quickly even if your disk is almost empty.
Real world file systems show a lot of aging, as well as free space fragmentation.
Claim: Only happens when
the disk is full
Recent work on aging
“File Systems Fated for Senescence? Nonsense, says Science!” Conway et. al. FAST 2017
“Geriatrix: Aging what you see and what you don’t see. A file system aging approach for modern storage systems” Kadekodi et. al. ATC 2018
On modern filesystems, aging is severe and happens quickly even if your disk is almost empty.
Real world file systems show a lot of aging, as well as free space fragmentation.
Aging is a problem
Disk fullness ????
Claim: Only happens when
the disk is full
Recent work on aging
“File Systems Fated for Senescence? Nonsense, says Science!” Conway et. al. FAST 2017
“Geriatrix: Aging what you see and what you don’t see. A file system aging approach for modern storage systems” Kadekodi et. al. ATC 2018
On modern filesystems, aging is severe and happens quickly even if your disk is almost empty.
Real world file systems show a lot of aging, as well as free space fragmentation.
Aging is a problem
Disk fullness ????
Claim: Only happens when
the disk is full
Flavors of Aging
Flavors of Aging
3 Flavors of Aging
Read Aging Write Aging Free SpaceFragmentation
Flavors of Aging
3 Flavors of Aging
Read Aging Write Aging Free SpaceFragmentation
Fragmentation of pages which are read together
Fragmentation of pages which are written together
Fragmentation of the available free space
ORAdditional work when writing
Flavors of Aging
Different types of aging interact
Free SpaceFragmentation
Fragmentation of the available free space
Flavors of Aging
Different types of aging interact
Free SpaceFragmentation
Fragmentation of the available free space
A filesystem:each square represents a page,different colors are different files
Flavors of Aging
Different types of aging interact
Free SpaceFragmentation
Fragmentation of the available free space
A filesystem:each square represents a page,different colors are different files
How do we write this large file?
Flavors of Aging
Different types of aging interact
Free SpaceFragmentation
Fragmentation of the available free space
A filesystem:each square represents a page,different colors are different files
How do we write this large file?
write it to available blocks
Flavors of Aging
Different types of aging interact
Free SpaceFragmentation
Fragmentation of the available free space
A filesystem:each square represents a page,different colors are different files
How do we write this large file?
write it to available blocks both read and write aging
Flavors of Aging
Different types of aging interact
Free SpaceFragmentation
Fragmentation of the available free space
A filesystem:each square represents a page,different colors are different files
How do we write this large file?
Flavors of Aging
Different types of aging interact
Free SpaceFragmentation
Fragmentation of the available free space
A filesystem:each square represents a page,different colors are different files
How do we write this large file?
defragment the free space
Flavors of Aging
Different types of aging interact
Free SpaceFragmentation
Fragmentation of the available free space
A filesystem:each square represents a page,different colors are different files
How do we write this large file?
defragment the free space lots of write aging
How much aging is caused by disk fullness?
This Work
This work tries to answer:How much aging is caused by disk fullness?
This Work
This work tries to answer:How much aging is caused by disk fullness?
Hypothesis:A lot
This Work
This work tries to answer:How much aging is caused by disk fullness?
Hypothesis:A lot
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Git Replay Benchmark
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
Git Replay Benchmark
get coffee
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
git pull
get coffeegit pull
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
git pull
make
get coffeegit pullmake
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
git pull
make
get coffeegit pullmakeget coffee
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
git pull
make
get coffeegit pullmakeget coffeegit pull
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
git pull
make
git pull
make
get coffeegit pullmakeget coffeegit pulladd awesome features
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
git pull
make
git pull
make
get coffeegit pullmakeget coffeegit pulladd awesome featuresget coffee
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
git pull
make
git pull
make
get coffeegit pullmakeget coffeegit pulladd awesome featuresget coffeegit pull
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
get coffeegit pullmakeget coffeegit pulladd awesome featuresget coffeegit pullfix bugs. . .
git pull
make
git pull
make
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
get coffeegit pullmakeget coffeegit pulladd awesome featuresget coffeegit pullfix bugs. . .
git pull
make
git pull
make
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
get coffeegit pullmakeget coffeegit pulladd awesome featuresget coffeegit pullfix bugs. . .
git pull
make
git pull
make
We need a workload that: • reflects actual use over many years• can be generated and replayed quickly• can operate on a nearly full disk
Let’s model a very simple case: Developers
Git Replay Benchmark
get coffeegit pullmakeget coffeegit pulladd awesome featuresget coffeegit pullfix bugs. . .
git pull
make
git pull
make
We can simulate a developer by replaying Git histories
Git Replay Benchmark
Use the Linux kernel repo from github.com
Do 100 git pulls
Measure Performance
How to Measure Aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
How to measure read aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
How to measure read aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
How to measure read aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
How to measure read aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
How to measure read aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
How to measure read aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
How to measure read aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
How to measure read aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
How to measure read aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
How to measure read aging
Measuring Aging
time grep -r random_string /path/to/filesystem
dir
file1 file2 file3 file4
Measure read aging by reading through all the files in directory order
Normalize by filesystem size
How to measure read aging
Git Replay Benchmark
Use the Linux kernel repo from github.com
Do 100 git pulls
Measure Performance
Git Replay Benchmark
Use the Linux kernel repo from github.com
Do 100 git pulls
Measure Performance
But what about when the disk fills up?
Git Replay Benchmark (full disk edition)
Git Replay Benchmark (full disk edition)
But what about when the disk fills up?
Use multiple copies of the repo
Linux1 Linux2
Linux4Linux3
Git Replay Benchmark (full disk edition)
But what about when the disk fills up?
Use multiple copies of the repo
Linux1 Linux2
Linux4Linux3
git pull
Git Replay Benchmark (full disk edition)
But what about when the disk fills up?
Use multiple copies of the repo
Linux1 Linux2
Linux4Linux3
git pullgit pull
Git Replay Benchmark (full disk edition)
But what about when the disk fills up?
Use multiple copies of the repo
Linux1 Linux2
Linux4Linux3
git pullgit pullgit pull
Git Replay Benchmark (full disk edition)
But what about when the disk fills up?
Use multiple copies of the repo
Linux1 Linux2
Linux4Linux3
git pullgit pullgit pullgit pull
Git Replay Benchmark (full disk edition)
But what about when the disk fills up?
Use multiple copies of the repo
Linux1 Linux2
Linux4Linux3
git pullgit pullgit pull
git pullgit pull
FAIL
Git Replay Benchmark (full disk edition)
But what about when the disk fills up?
Use multiple copies of the repo
Linux1 Linux2
Linux4Linux3
git pullgit pullgit pull
git pullgit pull
FAIL
When the disk fills and a pull fails, delete one
Full Disk Git Aging on HDD
grep
tim
e (s
econ
ds /
GiB
)
0
200
400
600
800
1000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged
Full Disk Git Aging on HDD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
500GiB 7200 RPMToshiba HDD
Ubuntu version 18.04 LTSLinux kernel v 4.15
grep
tim
e (s
econ
ds /
GiB
)
0
200
400
600
800
1000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged
Full Disk Git Aging on HDD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
500GiB 7200 RPMToshiba HDD
Ubuntu version 18.04 LTSLinux kernel v 4.15
The git replay benchmark quickly generates a big
drop in performance
grep
tim
e (s
econ
ds /
GiB
)
0
200
400
600
800
1000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged
Full Disk Git Aging on HDD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
500GiB 7200 RPMToshiba HDD
Ubuntu version 18.04 LTSLinux kernel v 4.15
The git replay benchmark quickly generates a big
drop in performance
But how much is from disk fullness?
Need to compare to non-full disks
How to compare to non-full disks
Linux1 Linux2
Linux4Linux3
We can’t just use a larger disk with the git replay benchmark
Linux6Linux5
Linux8Linux7
It’ll still just be full!
How to compare to non-full disks
Linux1 Linux2
Linux4Linux3
We can’t just use a larger disk with the git replay benchmark
It’ll still just be full!
We record the operations on the small disk and replay them on the larger disk
How to compare to non-full disks
Linux1 Linux2
Linux4Linux3
We can’t just use a larger disk with the git replay benchmark
It’ll still just be full!
We record the operations on the small disk and replay them on the larger disk
How to compare to non-full disks
Linux1 Linux2
Linux4Linux3
We can’t just use a larger disk with the git replay benchmark
It’ll still just be full!
We record the operations on the small disk and replay them on the larger disk
How to compare to non-full disks
Linux1 Linux2
Linux4Linux3
We can’t just use a larger disk with the git replay benchmark
It’ll still just be full!
We record the operations on the small disk and replay them on the larger disk
How to compare to non-full disks
Linux1 Linux2
Linux4Linux3
We can’t just use a larger disk with the git replay benchmark
It’ll still just be full!
We record the operations on the small disk and replay them on the larger disk
How to compare to non-full disks
Linux1 Linux2
Linux4Linux3
We can’t just use a larger disk with the git replay benchmark
It’ll still just be full!
We record the operations on the small disk and replay them on the larger disk
grep
tim
e (s
econ
ds /
GiB
)
0
200
400
600
800
1000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged ext4 empty aged
Full Disk Git Aging on HDD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
500GiB 7200 RPMToshiba HDD
Ubuntu version 18.04 LTSLinux kernel v 4.15
grep
tim
e (s
econ
ds /
GiB
)
0
200
400
600
800
1000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged ext4 empty aged
Full Disk Git Aging on HDD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
500GiB 7200 RPMToshiba HDD
Ubuntu version 18.04 LTSLinux kernel v 4.15
aging from fullness
grep
tim
e (s
econ
ds /
GiB
)
0
200
400
600
800
1000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged ext4 empty aged
Full Disk Git Aging on HDD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
500GiB 7200 RPMToshiba HDD
Ubuntu version 18.04 LTSLinux kernel v 4.15
aging from fullness
How can we be sure the performance drop is aging?
How to isolate aging
Unaged Baseline
Want an “unaged” baseline
Unaged Baseline
Want an “unaged” baseline
“What the file system would do if the data had always been there”
Unaged Baseline
Want an “unaged” baseline
“What the file system would do if the data had always been there”
Unaged baseline: Copy logical state to
empty filesystem
Unaged Baseline
Want an “unaged” baseline
“What the file system would do if the data had always been there”
Unaged baseline: Copy logical state to
empty filesystem
Do 100 git pulls
Measure (aged) performance
Unaged Baseline
Want an “unaged” baseline
“What the file system would do if the data had always been there”
Unaged baseline: Copy logical state to
empty filesystem
Do 100 git pulls
Measure (aged) performance
cp -a /mnt/aged/* /mnt/unaged/
Unaged Baseline
Want an “unaged” baseline
“What the file system would do if the data had always been there”
Unaged baseline: Copy logical state to
empty filesystem
Do 100 git pulls
Measure (aged) performance
cp -a /mnt/aged/* /mnt/unaged/
Measure (unaged) performance
Unaged Baseline
Want an “unaged” baseline
“What the file system would do if the data had always been there”
Unaged baseline: Copy logical state to
empty filesystem
Do 100 git pulls
Measure (aged) performance
cp -a /mnt/aged/* /mnt/unaged/
Measure (unaged) performance
grep
tim
e (s
econ
ds /
GiB
)
0
200
400
600
800
1000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged ext4 empty aged ext4 unaged
Full Disk Git Aging on HDD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
500GiB 7200 RPMToshiba HDD
Ubuntu version 18.04 LTSLinux kernel v 4.15
grep
tim
e (s
econ
ds /
GiB
)
0
200
400
600
800
1000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged ext4 empty aged ext4 unaged
Full Disk Git Aging on HDD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
500GiB 7200 RPMToshiba HDD
Ubuntu version 18.04 LTSLinux kernel v 4.15
usageaging
grep
tim
e (s
econ
ds /
GiB
)
0
200
400
600
800
1000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged ext4 empty aged ext4 unaged
Full Disk Git Aging on HDD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
500GiB 7200 RPMToshiba HDD
Ubuntu version 18.04 LTSLinux kernel v 4.15
usageaging
aging from fullness
Full Disk Git Aging on HDD (XFS and BTRFS)gr
ep ti
me
(sec
onds
/ G
iB)
0
200
400
600
800
1000
number of pulls performed0 2000 4000 6000 8000 10000
XFS full agedXFS empty agedXFS unaged
0
200
400
600
800
1000
number of pulls performed0 2000 4000 6000 8000 10000
BTRFS full agedBTRFS empty agedBTRFS unaged
XFS BTRFS
Full Disk Git Aging on SSD
grep
tim
e (s
econ
ds /
GiB
)
0
5
10
15
20
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged ext4 empty aged ext4 unaged
Full Disk Git Aging on SSD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
250 GiB Samsung860 EVO SSD
Ubuntu version 14.04 LTSLinux kernel v 3.11
grep
tim
e (s
econ
ds /
GiB
)
0
5
10
15
20
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
ext4 full aged ext4 empty aged ext4 unaged
Full Disk Git Aging on SSD (ext4)
Full:Empty:Unaged:
5GiB partition50GiB partition50GiB partition
System Details:
Dell PowerEdge T130
4-core 3.00 GHz Intel® Xeon(R) E3-1220 v6 CPU
16 GiB RAM
250 GiB Samsung860 EVO SSD
Ubuntu version 14.04 LTSLinux kernel v 3.11
0
5
10
15
20
0 2000 4000 6000 8000 10000
ext4 full agedext4 empty agedext4 unaged
Full Disk Git Aging on SSD (ext4)ext4
0
5
10
15
20
0 2000 4000 6000 8000 10000
BTRFS full agedBTRFS empty agedBTRFS unaged
BTRFS
0
5
10
15
20
0 2000 4000 6000 8000 10000
XFS full agedXFS empty agedXFS unaged
XFS
0
5
10
15
20
0 2000 4000 6000 8000 10000
F2FS full agedF2FS empty agedF2FS unaged
F2FS
What About Free Space Fragmentation?
Measuring AgingHow to measure free space fragmentation
Measuring Aging
e2freefrag on ext4
How to measure free space fragmentation
Measuring Aging
e2freefrag on ext4
How to measure free space fragmentation
“histogram over time”
MiB
in e
xten
ts o
f giv
en s
ize0
2000
4000
6000
8000
10000
4KiB-8KiB8KiB-16KiB16KiB-32KiB32KiB-64KiB64KiB-128KiB128KiB-256KiB256KiB-512KiB512KiB-1MiB1MiB-2MiB2MiB-4MiB4MiB-8MiB8MiB-16MB16MiB-32MiB32MiB-64MiB64MiB-128MiB128MiB-256MiB256MiB-512MiB512MiB-1GiB1GiB-2GiB
Measuring Aging
e2freefrag on ext4
How to measure free space fragmentation
“histogram over time”
MiB
in e
xten
ts o
f giv
en s
ize0
2000
4000
6000
8000
10000
4KiB-8KiB8KiB-16KiB16KiB-32KiB32KiB-64KiB64KiB-128KiB128KiB-256KiB256KiB-512KiB512KiB-1MiB1MiB-2MiB2MiB-4MiB4MiB-8MiB8MiB-16MB16MiB-32MiB32MiB-64MiB64MiB-128MiB128MiB-256MiB256MiB-512MiB512MiB-1GiB1GiB-2GiB
time
Measuring Aging
e2freefrag on ext4
How to measure free space fragmentation
“histogram over time”
MiB
in e
xten
ts o
f giv
en s
ize0
2000
4000
6000
8000
10000
4KiB-8KiB8KiB-16KiB16KiB-32KiB32KiB-64KiB64KiB-128KiB128KiB-256KiB256KiB-512KiB512KiB-1MiB1MiB-2MiB2MiB-4MiB4MiB-8MiB8MiB-16MB16MiB-32MiB32MiB-64MiB64MiB-128MiB128MiB-256MiB256MiB-512MiB512MiB-1GiB1GiB-2GiB
time
Git Replay Benchmark: Free Space Fragmentation
Full Disk Git Aging Free Space Fragmentation on ext4M
iB in
ext
ents
of g
iven
size
0
1000
2000
3000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
4KiB-8KiB8KiB-16KiB16KiB-32KiB32KiB-64KiB64KiB-128KiB128KiB-256KiB256KiB-512KiB512KiB-1MiB1MiB-2MiB2MiB-4MiB4MiB-8MiB8MiB-16MB16MiB-32MiB32MiB-64MiB64MiB-128MiB128MiB-256MiB256MiB-512MiB512MiB-1GiB1GiB-2GiBFull
Full Disk Git Aging Free Space Fragmentation on ext4M
iB in
ext
ents
of g
iven
size
0
1000
2000
3000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
4KiB-8KiB8KiB-16KiB16KiB-32KiB32KiB-64KiB64KiB-128KiB128KiB-256KiB256KiB-512KiB512KiB-1MiB1MiB-2MiB2MiB-4MiB4MiB-8MiB8MiB-16MB16MiB-32MiB32MiB-64MiB64MiB-128MiB128MiB-256MiB256MiB-512MiB512MiB-1GiB1GiB-2GiB
64MiB-128MiB
Empty
Full Disk Git Aging Free Space Fragmentation on ext4M
iB in
ext
ents
of g
iven
size
0
1000
2000
3000
number of pulls performed0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
4KiB-8KiB8KiB-16KiB16KiB-32KiB32KiB-64KiB64KiB-128KiB128KiB-256KiB256KiB-512KiB512KiB-1MiB1MiB-2MiB2MiB-4MiB4MiB-8MiB8MiB-16MB16MiB-32MiB32MiB-64MiB64MiB-128MiB128MiB-256MiB256MiB-512MiB512MiB-1GiB1GiB-2GiB
64MiB-128MiB
Unaged
What we learned
What we learned
Aging due to use >> aging due to fullness
Git benchmark:
What we learned
Aging due to use >= aging due to fullness
Worst case benchmark (see paper):
Aging due to use >> aging due to fullness
Git benchmark:
What we learned
Aging due to use >= aging due to fullness
Worst case benchmark (see paper):
Aging due to use >> aging due to fullness
Git benchmark:
Suggests that for most workloads,use aging is the first-order effect
What we learned
Aging due to use >= aging due to fullness
Worst case benchmark (see paper):
Aging due to use >> aging due to fullness
Git benchmark:
Suggests that for most workloads,use aging is the first-order effect
Disk Fullness
What we learned
Aging due to use >= aging due to fullness
Worst case benchmark (see paper):
Free-space fragmentation
Aging due to use >> aging due to fullness
Git benchmark:
Suggests that for most workloads,use aging is the first-order effect
Disk Fullness ⇒
What we learned
Aging due to use >= aging due to fullness
Worst case benchmark (see paper):
Free-space fragmentation
Aging due to use >> aging due to fullness
Git benchmark:
Suggests that for most workloads,use aging is the first-order effect
Disk Fullness File System Aging⇒ ⇒?
![Lab 1: Git - Hanyang · 2020. 3. 26. · 1. git init 2. git remote add [repoName] [url] 3. git pull [repoName] [branch(e.g. master)] 4. Working… 5. git add * 6. git commit –m](https://img.pdfslide.us/doc/110x75/5ff18f05f6668f333e2be74f/lab-1-git-hanyang-2020-3-26-1-git-init-2-git-remote-add-reponame-url.jpg)
