Charles Marcus wrote:
On 2011-10-25 6:14 AM, Linda Walsh <dovecot@tlinx.org> wrote:
and everyfrackin' body was using 4K packet sizes (at the application level!, the window size on TCP was over 64K...but no one was using it)....especially galling with my network's MTU at 9K, BTW, because small packets are really bad on a 1Gb network.
sendmail -- 4K, dovecot /ssl, 4K...
wazzup .. is t-bird forcing this,
If I'm not mistaken, yes, this is (or could be) a TBird problem... I can't find the bug report where this was discussed, but I distinctly remember one of the devs commenting on this 4k packet size issue. Apparently it was an intentional change, but he couldn't figure out why.
Fyi, it was discussed in one of the IMAP performance bugs...
Thanks for the lead...will check it out.The problem with the Tbird (and FF) is that design for home users with dialup connections, so if you have a home network and run IMAP @home, all their tuning goes out the window -- and they don't make it configurable.
I had to go to a 9K packet size on 1Gb ethernet to get close to full bandwitch usage (and then it is a large effort with a windows client)...and that's down at layer 2? FF IMAP is at layer 5? ... the latency is insane at that point.
Alot of companies aren't real bright when it comes to storing files locally -- instead of 'local' they almost always use the 'roaming' profile...Cuprits: TB@4G, Adobe@2.5G, XBMC ~1-2G. Adobe's great -- most of that 2.5G are the product helpfiles which you don't get when you install -- they are d/led later and thus stored in your roaming profile. Each user gets their own copy of the help material...
Of course good thing they got rid of customer input for product design and got rid of 'usability studies'... those things always caused problems. Like MS removing the start bar in Win8 cause users don't want it? Huh? or Cocacola switching to 'newCoke, then having to revert due to outcry...because Coke drinkers didn't want another pepsi knockoff.
Baka!