I can't answer you question on "work best",
but I can say that a month ago we changed our max frame size from
1496 to 5984.
We did it for the same reasons you spoke of, we have nightly batch
processes that FTP lots of data across a dark fibre connection (over
We haven't noticed any determent in the daily processes, and only
decreased the time of our nightly process by no more than 10%.
On 10/8/2012 10:34 AM, J Franz wrote:
> Our ethernet definitions still have the 1496 max frame size.--
> 1Gb ethernets(2), v6r1 (but not fiber)
> Would like to change to 8996 , but network side concerned the higher frame side
> will affect
> app performance with many .net apps accessing our db2.
> We have heavy interactive use in day, and big data export nightly (which is why
> idea to increase frame size).
> Any thoughts on what would work best.
> Jim Franz
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact