So, if I force the windows machines to 32K net buffer, what is the correct way
to handle the others daemons?
- should I force to 32K the sd too?
- should I force any other fd on the lan to 32k too?
- may I leave everything to default, but the windows machines?
At the moment I forced everything to 32k.
Gabriele Bulfon - Sonicle S.r.l.
Tel +39 028246016 Int. 30 - Fax +39 028243880
Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY
http://www.sonicle.com
----------------------------------------------------------------------------------
Da: Kern Sibbald <[EMAIL PROTECTED]>
A: bacula-users@lists.sourceforge.net
Cc: Gabriele Bulfon <[EMAIL PROTECTED]>
Data: 30 gennaio 2007 20.16.33 CET
Oggetto: Re: [Bacula-users] Solved why Windows FD 1.38 sometime is slow
Hello,
On Tuesday 30 January 2007 18:41, Gabriele Bulfon wrote:
> I had headaches for a week, trying to figure out why some windows FDs were
> VERY slow compared to all the rest of FDs. These slow clients were all
> rating at around 1Mb/s. After playing a bit with many system and bacula
> parameters, I decided not to trust what was stated in the manual: "the
> default Maximum Network Buffer Size = 32768". Because I tried rising this
> parameter to double default, both on sd and all fds, and noticed that I had
> a slow down of all the FDs, I put back everything to default.
> Then I decided to explicitly set the
> "Maximum Network Buffer Size = 32768" to the windows machine
> that was still so slow....and it magically started to work as the rest of
> fds!!!
Yes, you are right. The documentation is incorrect. The default was 32768
but was at some point changed to 65536, but the documentation did not get
updated. The 65536 works very well in the Unix/Linux environment, but as you
have discovered (absolutely amazing), it may not work on some network cards.
This was mentioned in the manual. However, I have now updated the manual to
have the correct default and to more clearly point out the potential
problems.
> Beacuse I have another windows FD on the same installation, with the
> same version of bacula, and this one was going fine with the default (MNB
> not specified), what I believe is that the windows setup has been built
> with a different default (maybe 65536), and this setting may be fine only
> in specific situations. What I mean, is that probably 32768 is fine for
> almost any card, but 65536 may be fine only for cards that support this
> buffer size.
> What I know now is that explicitly setting the buffer to 32768 on the
> bacula fd will work. After finding this, I did the same on other 3
> installations where I had similar problems, and it worked! Thanx to
> everyone that tried to help me.
Thanks to you for discovering it ...
Best regards,
Kern
> Gabriele.
> Gabriele Bulfon - Sonicle S.r.l.
> Tel +39 028246016 Int. 30 - Fax +39 028243880
> Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY
> http://www.sonicle.com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
