>How does one configure the blocksize?
Marc was (I assume) referring to old, crufty, icky, by hand scripts he
used in the far past, not wonderful, shiny Amanda :-). I fully intend
to ignore the fact that they were faster :-).
I think what he meant was he changed the 'b' flag value on the dump,
which increases the size of the write() call (and possibly some network
ioctl sizes).
I just ran a few quick tests on a system here with a 500 MByte image:
sendsize -> dumper -> holding disk 1994.1
sendsize -t (client only to /dev/null) 2104
simulated sendsize with named pipes 2103
ufsdump to /dev/null (no ufsrestore) 2118
Without going into detail about the various tests, they are all so
close on my system as to make essentially no difference (~ 1%).
>What about the blocksize used on the tape? perhaps that can be tuned, too...
Eventually, but this will have a lot of ripple effects (like how you
do restores without Amanda). And it doesn't affect the problem under
discussion in this thread, which is why the dump to disk (actually,
to/through the network) is slower than would seem reasonable.
>g.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
