You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would Canonical be interested in seeing (or helping) zfs-unlimited move forward?
I feel currently some limitations are preventing ZFS from realizing its full potential. To quote this arstechnica article: "once you accumulate a few thousand snapshots, you can begin seeing filesystem performance issues".
I noticed ZFS's limitations in the middle of my personal project, which I started in 2018 without knowing Canonical was working on ZSys with similar objectives.
The zfs-unlimited patch was my response to the performance issues I experienced. Had to read through about half of the ZFS codebase and try many things before settling on the shortest path solution (and feeling confident nothing got seriously messed up).
Three and half years later, a lot of work is needed to bring it up to date. If I could get some (at least moral) support that would great.
The text was updated successfully, but these errors were encountered:
Self-promoting here ...
Would Canonical be interested in seeing (or helping) zfs-unlimited move forward?
I feel currently some limitations are preventing ZFS from realizing its full potential. To quote this arstechnica article: "once you accumulate a few thousand snapshots, you can begin seeing filesystem performance issues".
I noticed ZFS's limitations in the middle of my personal project, which I started in 2018 without knowing Canonical was working on ZSys with similar objectives.
The zfs-unlimited patch was my response to the performance issues I experienced. Had to read through about half of the ZFS codebase and try many things before settling on the shortest path solution (and feeling confident nothing got seriously messed up).
Three and half years later, a lot of work is needed to bring it up to date. If I could get some (at least moral) support that would great.
The text was updated successfully, but these errors were encountered: