On Thu, Apr 23, 2009 at 06:09:55PM +0200, Thomas Pfaff wrote: > On Thu, 23 Apr 2009 15:31:58 +0200 > Tobias Ulmer <tobi...@tmux.org> wrote: > [...] > > > > > Try: time tar -zxf ports.tar.gz && sync > > > > > > > > And include the output of mount and show the place where you are > > > > untarring. > > > > > > > > > > $ mount > > > /dev/wd0a on / type ffs (local, softdep) > > > /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) > > > fs:/pub on /pub type nfs (nodev, noexec, nosuid, v3, udp, timeo=100) > > > > > > $ pwd > > > /home/tpfaff > > > > > > $ time tar -zxf ports.tar.gz && sync # (... && sync) ~same result > > > 1m2.66s real 0m1.09s user 0m6.85s system > > > $ time rm -rf ports > > > 0m15.20s real 0m0.15s user 0m1.42s system > > > > and on linux? > > First on Ubuntu: > > Script started on Thu 23 Apr 2009 03:50:27 PM CEST > ~$ time (tar -zxf ports.tar.gz && sync) > real 0m47.784s > user 0m1.576s > sys 0m5.024s > ~$ time (rm -rf ports && sync) > real 0m1.883s > user 0m0.076s > sys 0m1.664s > time (tar -zxf ports.tar.gz && sync) > real 0m20.652s > user 0m1.240s > sys 0m2.592s > ~$ time (rm -rf && sync) > real 0m0.003s > user 0m0.004s > sys 0m0.004s > ~$ time tar -zxf ports.tar.gz > real 0m11.513s > user 0m1.268s > sys 0m2.772s > ~$ time rm -rf ports > real 0m1.752s > user 0m0.100s > sys 0m1.648s > ~$ time tar -zxf ports.tar.gz > real 0m14.400s > user 0m1.352s > sys 0m2.560s > ~$ time rm -rf ports > real 0m1.756s > user 0m0.076s > sys 0m1.684s > ~$ mount # watch your eyes! > /dev/sda2 on / type ext3 (rw,relatime,errors=remount-ro) > proc on /proc type proc (rw,noexec,nosuid,nodev) > /sys on /sys type sysfs (rw,noexec,nosuid,nodev) > varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755) > varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777) > udev on /dev type tmpfs (rw,mode=0755) > devshm on /dev/shm type tmpfs (rw) > devpts on /dev/pts type devpts (rw,gid=5,mode=620) > lrm on /lib/modules/2.6.24-19-generic/volatile type tmpfs (rw) > securityfs on /sys/kernel/security type securityfs (rw) > gvfs-fuse-daemon on /home/tpfaff/.gvfs type fuse.gvfs-fuse-daemon > (rw,nosuid,nodev,user=tpfaff) > ~$ pwd > /home/tpfaff > ~$ exit > Script done on Thu 23 Apr 2009 03:53:20 PM CEST > > Then the same commands on OpenBSD: > > Script started on Thu Apr 23 17:55:53 2009 > $ time (tar -zxf ports.tar.gz && sync) > 1m2.62s real 0m1.15s user 0m7.15s system > $ time (rm -rf ports && sync) > 0m14.24s real 0m0.14s user 0m1.53s system > $ time (tar -zxf ports.tar.gz && sync) > 1m1.37s real 0m1.31s user 0m7.18s system > $ time (rm -rf ports && sync) > 0m14.72s real 0m0.12s user 0m1.82s system > $ time tar -zxf ports.tar.gz > 1m3.39s real 0m1.08s user 0m6.69s system > $ time rm -rf ports > 0m15.41s real 0m0.12s user 0m1.38s system > $ time tar -zxf ports.tar.gz > 1m2.62s real 0m1.19s user 0m6.80s system > $ time rm -rf ports > 0m15.63s real 0m0.10s user 0m1.79s system > $ mount > /dev/wd0a on / type ffs (local, softdep) > /dev/wd0k on /home type ffs (local, nodev, nosuid, softdep) > fs:/pub on /pub type nfs (nodev, noexec, nosuid, v3, udp, timeo=100) > $ pwd > /home/tpfaff > $ exit > Script done on Thu Apr 23 18:02:13 2009 >
ext3 and ffs are very different. So the same thing may take a different time to finish on either system because of different design decisions. >From your benchmark it seems your server's only purpose is to untar and remove ports.tar.gz in a loop or what are you trying to show? I'm very happy that OpenBSD ffs is a bit slower then Linux ext3. -- :wq Claudio
