Page 1 of 1

MTU parameter settings and network performance

Posted: Wed Oct 22, 2008 12:50 pm
by Steve Rowe
I'm convinced that there used to be a setting in the client (?) config file that allowed you to set the MTU for network packets. This seems to have disappeared, I can see no trace in the v9 or v8 documentation that I have. I've checked both server and client side configs.

Can anyone confirm my recollection?

On a slightly wider point is there a way of tuning the TM1 software to optmise it's perfomance on a partcular network? There's a variety of things you can do to the design of your TM1 application to make it run faster or slower. What I'm looking for is confguration options ,like the MTU=X one I'm sure used to exist, if there are any parameters I've missed I'd be grateful to hear of them.

Cheers,

Re: MTU parameter settings and network performance

Posted: Wed Oct 22, 2008 1:30 pm
by Martin Erlmoser
as far as i know applix took the mtu setting out with version 8.x or something like that. (they only use the mtu size defined by the nic / os)

i don't think that there are any network settings with which you can optimize the network performance

sorry - i really hope that somebody knows more.

Re: MTU parameter settings and network performance

Posted: Wed Oct 22, 2008 1:51 pm
by Steve Vincent
Copied from the admin guide for 8.1.8 for the tm1s.cfg file;
Parameter = NetworkFrame
Required or Optional = Optional
Cmd Line Equiv = -f

Description
This parameter sets the maximum transmission unit
(MTU) for the iTM1 packet. This is a four-digit number
that iTM1 sets based on your network configuration.
The default is 0, which directs iTM1 to pick up the
optimized packet size from the network. This size is
usually 1460 bytes.
If you encounter performance issues, reset this number.
To determine the optimum packet size, ping the remote
server, and subtract 12 from the result
Have checked 9.0 and its not mentioned so it does appear they removed it. If i'm honest i can't blame them either, having an application with a different MTU to the network it resides on can only lead to bad things :(