Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jjobi
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
by
jjobi
10y ago
SSD was used as the backend device for the tests. If a file is used for LCFS backend, the performance will be limited by the underlying file system in which the file is hosted. LCFS is capable of working directly on top of device and can q
2.
▲
by
jjobi
10y ago
hi, I'm the author of LCFS, let me know if you have any questions about how it works or how we measured the performance.
3.
▲
by
jjobi
10y ago
This was done using fuse to make it portable across different distros. We have not seen any major issues testing it as a docker storage driver, compared to the graphdrivers in use today.
4.
▲
by
jjobi
10y ago
It is a mini-file system, working directly on top of a block device. Having something else in between is not a good idea. Much of the data handled by docker storage driver is temporary and does not even have to hit disk before thrown away
5.
▲
by
jjobi
10y ago
I would say image layer file system is not that hard to solve if you approach the problem correctly. It looks like all prior attempts tried to use general purpose solutions and in some cases a combination of those (for example, overlay on
6.
▲
by
jjobi
10y ago
There are many problems a storage driver for docker need to solve. We are not replacing docker here, just providing a better solution for the storage driver (API of which is defined by docker) part of it. Solutions in use today are half b
7.
▲
by
jjobi
10y ago
This is not a general purpose file system, but something purpose built for serving as a docker storage driver. LCFS outperforms existing solutions and does not have any correctness issues. It is an experimental release at this point. We w
8.
▲
by
jjobi
10y ago
BTRFS has so many drawbacks using it as storage driver for docker. See the bottom of the page https://docs.docker.com/engine/userguide/storagedriver/btrfs... . Primary drawback being each container creates un
9.
▲
by
jjobi
10y ago
Again, the focus of this blog is not about a de-duplication story, but about a new docker storage driver.
10.
▲
by
jjobi
10y ago
This is a custom built solution for docker storage driver. A de-duplication server cannot be docker storage driver, as there are more things involved in a docker storage driver like layer management, rapid cloning and deletion of those, ef
11.
▲
by
jjobi
10y ago
We did not solve a typical de-duplication problem with LCFS. If you write two copies of the same data to LCFS, there will be two copies of data stored. We may provide such de-duplication feature at some point in future. Docker is already
12.
▲
by
jjobi
10y ago
The README is updated with more details on the tests performed. Also concerns raised about setup scripts are fixed now. Thanks a lot for pointing those out. I am not surprised on your first impression that the published results are too go
13.
▲
by
jjobi
10y ago
Yes, it is a native file system optimized for large number of containers (clones), sharing read only image layers. LCFS also understands the ephemeral nature of data stored in /var/lib/docker and avoids some of the complexit
14.
▲
by
jjobi
10y ago
Yes, also it does not have data corruption issues reported with overlays (readers vs writers). Also it supports atomic rename. NO whiteouts required as in the case of a union file systems (so not to worry about deleted files coming back).