Re: Relative performance of swap-backed MFS vs. regular UFS?

From: Dag-Erling Smørgrav (des_at_des.no)
Date: 10/23/04

  • Next message: Ryan Sommers: "Re: bootable install CD - relocate to subdir"
    To: Clifton Royston <cliftonr@lava.net>
    Date: Sat, 23 Oct 2004 16:10:41 +0200
    
    

    Clifton Royston <cliftonr@lava.net> writes:
    > For a large temporary file system which must hold short-lived files,
    > mostly small but occasionally several very large ones (e.g. 100MB+), is
    > it better for performance and stability if this file system:
    >
    > 1) resides on a swap-backed MFS and trusts the OS to swap out
    > low-priority blocks if needed under RAM pressure, or
    >
    > 2) on a regular UFS and trusts the OS to buffer as many blocks as
    > possible into RAM when RAM is free?

    the former, provided you have enough RAM. A swap-backed MFS will only
    swap out when it has to, while a UFS will always write out changes
    after a while.

    > I temporarily enlarged it to 256MB which is working, but as I worked
    > out the worst case scenario, I realized it really would need to be
    > nearly 1GB to handle multiple zip-bombs each hitting the 100MB size
    > limit. This makes me wonder if it's wise to specify a 1GB MFS on a
    > system with only 1GB RAM, or wiser to just revert to a regular file
    > system?

    RAM is cheap. Toss in a couple extra gig and set up a 2 GB MFS.

    DES

    -- 
    Dag-Erling Smørgrav - des@des.no
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
    

  • Next message: Ryan Sommers: "Re: bootable install CD - relocate to subdir"

    Relevant Pages

    • OT/drift: when is a RAMdisk an appropriate solution
      ... include the "ram disk" component in your project. ... Sometimes, a physical RAM ... only to wind up going directly to regular old ordinary memory, ... testing the file system software. ...
      (comp.lang.c)
    • Re: How to Add RAM File System
      ... RAM disk build as part of a Windows CE configuration. ... RAMDISK to use in my Windows Mobil application. ... File System into my catalog, ...
      (microsoft.public.windowsce.embedded)
    • Re: Prefetch Abort in FileSys
      ... looks at a few magic variables to decide if the RAM contents are valid. ... RAM is in a random state and will easily cause a file system ... NKForceCleanBootAPI in OEMInit to ensure that the filesystem is ... >> Errors like this are almost always problems in memory setup. ...
      (microsoft.public.windowsce.platbuilder)
    • Re: Large Dictionaries
      ... Wed May 17 16:35:59 2006 StorageBerkeleyDB population stopped, ... Ok, according to the Windows task manager the Python process reads/writes to the file system during the run of BerkeleyDB test around 7 GByteof data and the hard drive is continuously busy, where the size of file I found in the Temp directory is always below 20 MByte. ... Can the BerkeleyDB via Python bsddb3 interface be tuned to use only RAM or as BerkeleyDB can scale to larger data amount it makes not much sense to tweak it into RAM? ...
      (comp.lang.python)
    • Re: G5 ECC (was Re: X-serve verses G5s)
      ... concepts as "journaling" with no problem whatever, ... They never stop to consider that some, if not all, of the file system ... single bit ram failures. ... need to get a memory error on the in-memory copy of file system data ...
      (comp.sys.mac.system)