Browse Prior Art Database

Auto Tuning for Network Software

IP.com Disclosure Number: IPCOM000115686D
Original Publication Date: 1995-Jun-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 91K

Publishing Venue

IBM

Related People

Anand, VK: AUTHOR

Abstract

Software products in a system are layered in different levels. This helps the top level software to be portable. Hardware specific software are at the bottom level. Intermediate level software provides framework, etc. Developers of the framework have knowledge which needs to be shared with the application layer software developers and the ultimate users. Most of the working knowledge of the product is gained during the test phases. In the arena of network, protocols form this framework layer. Usually the network protocols have parameters that can be configured for different situations. Tuning these parameters become crucial for some environments to function properly. There are various factors that needs to be taken into consideration for tuning.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Auto Tuning for Network Software

      Software products in a system are layered in different levels.
This helps the top level software to be portable.  Hardware specific
software are at the bottom level.  Intermediate level software
provides framework, etc.  Developers of the framework have knowledge
which needs to be shared with the application layer software
developers and the ultimate users.  Most of the working knowledge of
the product is gained during the test phases.  In the arena of
network, protocols form this framework layer.  Usually the network
protocols have parameters that can be configured for different
situations.  Tuning these parameters become crucial for some
environments to function properly.  There are various factors that
needs to be taken into consideration for tuning.  It becomes more
complicated for human mind when various combination of different
factors need to be considered.  To make these network products easy
for any customer to use, there is a need to find a way to get this
information to end users in more appealing and easy to understand
way.  This invention discusses two ways to make tuning and
customizing a network software easy.

      Incorporating the knowledge that the development team has
acquired about the tuning and customizing the configurations to
different network structure into a knowledge base would help the end
user.

      An user by using the above mentioned knowledge base should be
able produce the customized configuration files for his network.  An
user should be able to layout his network structure, mark the
workstations where the network software to be installed through a
easy to use graphical interface.

      There are two types of configuration parameters 1.  protocol
specific 2.  software implementation specific.  The first category
can be used for any product that uses this protocol the second
category can be used only when the user use that particular product.
Developing a knowledge base with two parts one for protocol specific
and another for implementation specific would help to reuse the
knowledge base when the implementation changes during future
releases.

      Tuning and customizing the NTS/2 NetBIOS protocol of IBM* is
taken as an example in the following discussion:
  1.  T1 value, dlcretries and send timeout need to be increased when
       the network layout has bridges gateways etc.,
  2.  Receive buffer size should be...