Filesystem performance overheads?

From: sg (sachgarg_at_gmail.com)
Date: 05/11/05

  • Next message: sg: "Re: Switching from and to read-only file systems" 
    Date: 10 May 2005 20:18:30 -0700

    Hi all,

    Is anyone aware of studies that have been done to measure the
    performance overheads that result from using a filesystem? We want to
    know the performance loss that we would suffer using a filesystem like
    FAT16 on a ramdisk versus using the memory as it is (raw reads and
    writes to memory, without considering it as a ramdisk with a file
    system).

    As far as I understand the performance loss would be miniscule,
    especially compared to what the filesystem buys us in convenience. But,
    still I am looking for some hard facts to back up this claim.

    Thanks & regards,
    Sachin

  • Next message: sg: "Re: Switching from and to read-only file systems"

    Relevant Pages

    • Re: Filesystem performance overheads?
      ... > know the performance loss that we would suffer using a filesystem like ... > writes to memory, without considering it as a ramdisk with a file ...
      (comp.os.linux.misc)
    • Filesystem performance overheads?
      ... know the performance loss that we would suffer using a filesystem like ... writes to memory, without considering it as a ramdisk with a file ... As far as I understand the performance loss would be miniscule, ...
      (comp.os.linux.misc)
    • Re: Filesystem performance overheads?
      ... >performance overheads that result from using a filesystem? ... >know the performance loss that we would suffer using a filesystem like ... Raw read/writes don't have any of this overhead. ...
      (comp.os.linux.misc)
    • AIX 5.2 maxperm & Oracle
      ... maxperm was set to 63%, ... large volumes of data IO going through the AIX filesystem cache). ... for memory with filesystem cache. ...
      (comp.unix.aix)
    • Re: compiling root filesystem into kernel (preferably tmpfs root filesystem)
      ... compiling root filesystem into kernel ... (read only roots backed by media other than memory). ... Next, DO NOT compress the image with mkuzip, instead do: ...
      (freebsd-hackers)