<<< Chronological Index >>>    <<< Thread Index >>>

kauri first results


Hi Gerard,

I have copied the root software from ginkgo to my homedir on kauri
and made a symbolic link in /usr/local.

For duration of transition period, I've also mounted two of ginkgo's
filesystems; I may have to add few more and add that to the fstab
(so they survive reboot). However, once we've reached our final
setup, I expect kauri to not need any NFS mounts anymore.

A first test on speed and ROOT software was to run our delayplots
program (from the ginkgo mounted filesys) and compare with ginkgo:

  kauri:/export/nccfs4/home/wilhelm /usr/bin/time \
	delayplots -o ./tmp -s 01 -t 47 -f ps -m 500 -p 20001001/P30D

  ginkgo:/export/nccfs4/home/wilhelm /usr/bin/time \
        delayplots -o ./tmp -s 01 -t 47 -f ps -m 500 -p 20001001/P30D

Results:

- the PS files created are identical (except for creationdate comment)
- kauri is ~40% faster than ginkgo;

  for two runs of the above command the timings were:

		    real   user  system	    real  user system
	kauri:	    42.8   35.1    0.7      35.5  35.1  0.2
	ginkgo:	  1:08.0   48.9    0.7    1:20.5  48.4  0.6

  real time on ginkgo is higher than user time because of backup (dump)
  started from spruce at 16:16

Next week, after ops have moved the machine to a nice location in 
a rack, I will look into starting the (new) TTM plots-on-demand
service on this machine. Although in the end we expect it to be run
from ginkgo, it is better to first start it on kauri so we make the
most of the SUN power available to us. Migrating daily processing
and the tracerouteDB to kauri requires more time and needs to be
done with great care.

-- Rene
  

  

   






<<< Chronological Index >>>    <<< Thread Index >>>