On Wed, Nov 05, 2008 at 11:12:01AM +0100, Ulrich Leodolter wrote:
> Hello,
>
> Problem:
>
> Settings like (documented in the Manual)
>
> Minimum block size = 64K
> Maximum block size = 200K
>
> do not work. Both are defined as size_pint32.
> multipliers like K M are not allowed.
> don't know if this is intended,
> maybe documentation just a little outdated.
>
>
> Question:
>
> Can i expect performance improvements (especially for
> Copy/Migrate Disk to Tape jobs) by by increasing
> "Maximum block size" on File devices in bacula-sd.conf ???
>
> Device {
> Name = FileStorage
> Media Type = File
> Archive Device = /disk0/bacula/files
> LabelMedia = yes;
> Random Access = Yes;
> Requires Mount = No;
> AutomaticMount = yes;
> RemovableMedia = no;
> AlwaysOpen = no;
> MaximumBlockSize = 1048576; # 1M
> }
>
I think it should make difference at least with tape drives..
You can measure the difference with dd:
dd if=/dev/null of=/dev/tape bs=<try_different_block_sizes_here>
4k, 64k, 256k, 1MB, 4MB etc.
-- Pasi
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
