Project

General

Profile

Rbd - shared read cache » History » Version 1

Jessica Mack, 06/07/2015 01:22 AM

1 1 Jessica Mack
h1. Rbd - shared read cache
2
3
h3. Summary
4
5
RBD caching is currently in-memory and per-image. If many images are created from the same base image, memory is wasted trying to cache the parent image for each one. A shared cache would improve cache efficiency, since more of the common parent images could be cached, and there would be no duplicate caching of the same image in many processes. The cache could also be persistent, so there's no need to repopulate it if the host restarts. To simplify the implementation and avoid introducing potential data-losing bugs, this cache could be only a read-only cache, initially just for parent snapshots, which by definition cannot be written to. This avoids any coordination for cache invalidation as well.
6
7
h3. Owners
8
9
* Name (Affiliation)
10
* Name (Affiliation)
11
* Name
12
13
h3. Interested Parties
14
15
* Josh Durgin (Inktank)
16
* Haomai Wang (UnitedStack)
17
* Anip Patel (Arizona State University(student))
18
19
h3. Current Status
20
21
Currently caching is provided by the ObjectCacher class, which does writeback or writethrough caching. This cache would supplement that with a shared read cache, which may or may not be persistent.
22
23
h3. Detailed Description
24
25
TBD
26
27
h3. Work items
28
29
h3. Coding tasks
30
31
# Task 1
32
# Task 2
33
# Task 3
34
35
h3. Build / release tasks
36
37
# Task 1
38
# Task 2
39
# Task 3
40
41
h3. Documentation tasks
42
43
# Task 1
44
# Task 2
45
# Task 3
46
47
h3. Deprecation tasks
48
49
# Task 1
50
# Task 2
51
# Task 3