|
|
About ::
TODO ::
Blog ::
RSS ::
Old blog ::
Projects ::
GIT ::
Gallery ::
Notes
Wed, 26 Mar 2008
Climbing evening.
That was hard training, since I climb once per week (this year so far) only,
I can not get my the best shape, mostly in resistance part, so fingers
were rubbed quite quickly...
Nevertheless I finished my
jumpings
and reached the needed hold. Jump actually was not that high - about 30-40 santimeters,
but it should be done from holds which are about 2 meters below the final hold,
so it was not that simple, especially when holds for arms are only 10 santimeters
higher than that for legs, and main body's chakra (it is a nice name for the ass
in my own public dictionary) really does not like to fly and wants to land.
Then I did number of various starts, some with jumps, others were just usual
complex traces without additional requirements from me...
Evening sauna, shower and great pleasure of the day.
Excellent time!
/life :: Link / Comments (0)
Added maildir benchmark results.
The simulation works on each filesystem in the following stages:
- The empty filesystem is created and mounted.
- The directory structure is created, with no files.
- A single delivery simulator and retrieval simulator are run
simultaneously. The script waits for each of the simulators to finish,
and then runs the sync command before proceding to the next
step.
- The above step is repeated with 2, 4, 8, and then 16 delivery simulators.
Delivery Simulator.
The delivery simulator does actual maildir deliveries to the given directory:
- It writes a file with a unique file name to the tmp subdirectory.
- It fsyncs the newly written file.
- It renames the file into the new subdirectory.
- It fsyncs the new subdirectory (to ensure that
directory is actually on disk, as most Linux filesystems don't
automatically perform this action during the rename).
More details on original page.
Briefly saing, it is multithreaded maildir simulation.
And results
are quite different compared to for example postmark: very good results from xfs, jfs and reiserfs.
There are no ext2 and btrfs filesystems, since perl's fsync says that
filedescriptor opened there is invalid:
Invalid argument at /root/fs_bench/maildir_fsbench/fsbench/fake-deliver line 38.
Interested reader can check sources and show me a problem, but ext2 worked pretty fine with
2.6.20 kernel and to date glibs/perl/whatever was in Debian.
Anyway, results can be found at contest
homepage.
Now all testing is over.
Main conclusion: things got worse compared to 2.6.20 and there was no major breakthrough in filesystem development at least
from perfomance point of view.
/devel/fs :: Link / Comments (0)
Additional XFS test with slightly diferent mount/mkfs options.
mkfs: -d agcount=75 -l size=64m
mount: logbufs=8,nobarrier,noatime,nodiratime,osyncisdsync
Postmark results:


Results are slightly better than
previous
xfs run, although barriers are turned off, which I blame to be the main reason. Other
filesystems did not turn off directory atime also.
Anyway, even with this results XFS is still much worse than any other FS (except reiserfs)
for this workload.
/devel/fs :: Link / Comments (0)
|