Be aware that garbage collection will take quite a while on a full drive to go back to 0 unless you also increase the segments cleaned per run and if you accidentally leave it high it will impact performance.
This is why I had asked about a way to force a full GC with a protection period other than that in the conf file. It seems like quick forced cleanup when a user deletes a lot of files is a common need... Byron On Sep 26, 2009, at 11:08 AM, Jeff Layton <[email protected]> wrote: > Jérôme Poulin wrote: >> On Sat, Sep 26, 2009 at 10:36 AM, Jeff Layton <[email protected]> >> wrote: >> >>> Jérôme Poulin wrote: >>> >>> Cool program - I will definitely try this. >>> >>> So, let me summarize what I think I should do to test nilfs with >>> IOzone without the impact of the checkpoints and without filling >>> up the space. >>> >>> - Run IOzone without cleanerd running to minimize the >>> impact of checkpoints on IO performance. >>> - Assuming I don't fill up the file system, after a run of >>> IOzone, I need to run cleanerd but put the protection >>> period to something very small (e.g. 1 second) to reclaim the >>> space. >>> - Shut down cleanerd again and run another IOzone test. >>> (rinse and repeat) >>> >>> Does this sound about right? >>> >>> Thanks! >>> >>> Jeff >>> >>> >> That sounds right, either run cleanerd or mkfs the partition again >> for >> faster results ;) >> > > Good point about using mkfs. :) > > I think I'm going to run two test: (1) using the process above, (2) > setting > the protection period to 1 (maybe 0). Let's see what the differences > are. > > Thanks! > > Jeff > > _______________________________________________ > users mailing list > [email protected] > https://www.nilfs.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
