Hello all, I have to compare different filesystems options for an embedded platform and I'd like understand what's the best way in your opinion, I use to read wikipedia but do you have any suggestion or articles or references that can help me ? I am not really expert about filesystem but I have to start! Thanks, Pietro.
On Mon, 15 Apr 2013 16:24:17 +0200, Pietro Paolini said:
I have to compare different filesystems options for an embedded platform
Step 0: Get an accurate list of what requirements the embedded platform has. Is the storage flash based? Spinning oxide? What are the relative read/write ratios (some systems will have almost no writes, but a Tivo will have almost as many writes as reads (possibly more, even). What sustained rates of file I/O and metadata activity will you expect? Do you have a fairly high CPU budget and can afford more cycles, or are you using a slower ARM and have to do it with as few cycles as possible? How big will the filesystem be? How many meg/gig of data, and how many files? Small numbers of honking-huge files, or zillions of 139 byte files? Does the filesystem have to support TRIM or whiteouts? Plus any application specific issues I may have overlooked... Step 1: for i in $filesystems; do compare_specs($needed_specs, $i); done. You get the idea.
On Apr 15, 2013, at 6:26 PM, Valdis.Kletnieks@vt.edu wrote:
On Mon, 15 Apr 2013 16:24:17 +0200, Pietro Paolini said:
I have to compare different filesystems options for an embedded platform
Step 0: Get an accurate list of what requirements the embedded platform has. Is the storage flash based? Spinning oxide? What are the relative read/write ratios (some systems will have almost no writes, but a Tivo will have almost as many writes as reads (possibly more, even). What sustained rates of file I/O and metadata activity will you expect? Do you have a fairly high CPU budget and can afford more cycles, or are you using a slower ARM and have to do it with as few cycles as possible? How big will the filesystem be? How many meg/gig of data, and how many files? Small numbers of honking-huge files, or zillions of 139 byte files? Does the filesystem have to support TRIM or whiteouts? Plus any application specific issues I may have overlooked...
Step 1: for i in $filesystems; do compare_specs($needed_specs, $i); done.
You get the idea.
Thanks for the smart question, I know the answer for some of them but I realised I have to do further investigation on regarding my system needs. Regarding the Step 1 : where do you usually find specs ? There is somethings like RFC for filesystem ? needed_specs=$() ? :-) Thanks Pietro.
On Mon, Apr 15, 2013 at 1:53 PM, Pietro Paolini <pulsarpietro@aol.com>wrote:
On Apr 15, 2013, at 6:26 PM, Valdis.Kletnieks@vt.edu wrote:
On Mon, 15 Apr 2013 16:24:17 +0200, Pietro Paolini said:
I have to compare different filesystems options for an embedded platform
Step 0: Get an accurate list of what requirements the embedded platform has. Is the storage flash based? Spinning oxide? What are the relative read/write ratios (some systems will have almost no writes, but a Tivo will have almost as many writes as reads (possibly more, even). What sustained rates of file I/O and metadata activity will you expect? Do you have a fairly high CPU budget and can afford more cycles, or are you using a slower ARM and have to do it with as few cycles as possible? How big will the filesystem be? How many meg/gig of data, and how many files? Small numbers of honking-huge files, or zillions of 139 byte files? Does the filesystem have to support TRIM or whiteouts? Plus any application specific issues I may have overlooked...
Step 1: for i in $filesystems; do compare_specs($needed_specs, $i); done.
You get the idea.
Thanks for the smart question, I know the answer for some of them but I realised I have to do further investigation on regarding my system needs.
Regarding the Step 1 : where do you usually find specs ? There is somethings like RFC for filesystem ?
This is a pretty exhaustive list, but good as a starting point. http://en.wikipedia.org/wiki/Comparison_of_file_systems#Features
needed_specs=$() ? :-)
Thanks Pietro.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- Thanks - Manish
On Mon, Apr 15, 2013 at 7:24 AM, Pietro Paolini <pulsarpietro@aol.com>wrote:
Hello all, I have to compare different filesystems options for an embedded platform and I'd like understand what's the best way in your opinion, I use to read wikipedia but do you have any suggestion or articles or references that can help me ? I am not really expert about filesystem but I have to start!
Thanks, Pietro.
Hi Pietro, I think having answers to below questions will help you decide on the filesystem you want to choose. -> What kind of workload is it going to support -> big files / small files / avg file size ? -> Flat directory structure / Nested deep hierarchy of directories -> Write once read many times / or frequent overwrites / or append only workloads etc. -> Will it have frequent metadata updates as opposed to user writes (things like chmod, mv etc.) -> How much memory you will have -> Type of disks -> Will you need versioning or snapshot of your files -> Will you ever need to backup (incremental) -> Will you need to resize etc. etc., you get the idea. -- Thanks - Manish
participants (3)
-
Manish Katiyar -
Pietro Paolini -
Valdis.Kletnieks＠vt.edu