Kbase 1235: How to improve performance on DOS LAN Networks
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
How to improve performance on DOS LAN Networks
900621-jao03
INTRODUCTION: Date Last Modified: 04/31/93
=============
This Technical Support Knowledgebase entry suggests ways to improve
performance on a DOS LAN network (DOS SERVER PRODUCT)
WHY YOU'LL NEED TO:
===================
To achieve optimal performance on a DOS Local Area Network, there are
many factors to be taken into consideration. Often, performance is
dependent on the actual network configuration. This Knowledgebase
entry highlights some of the tuneable adjustments you can make to speed
your LAN performance.
PROCEDURAL APPROACH:
====================
1. Examine your DOS PATH
The only subdirectories which should be included in your DOS PATH
are those which contain files that end with .exe, .com or .bat.
If you have included the subdirectories which contain .r's or
.p's (PROGRESS procedures and compiled objects), they should be
removed from your DOS PATH.
Next, place \DLC (the directory where PROGRESS is installed) first
in your DOS PATH. Following this, place \DLC\LAN (the directory
where the PROGRESS LAN modules are installed). This allows the
appropriate executable to be found without searching subdirectories
which do not contain Progress files.
2. Examine your PROPATH
The only subdirectories that should appear in your PROPATH are
those which contain .r's and .p's (PROGRESS procedures and compiled
objects). In a development enviroment it is best to have \DLC
first in the PROPATH. While in a runtime environment, it is best to
place subdirectories which contain the application .r's first.
3. Look at the location of files
If possible, place the compiled procedures (.r's) on the local
hard disk of each users' workstation since it can take a
significant amount of time to transfer .r's across a network
each time a user runs another procedure.
Keep the PROGRESS temporary files on the local hard disk of each
users' workstation. Use the PROGRESS Temporary Directory (-T)
start-up option to relocate the temporary files.
Some network operating systems contain features which eliminate
bottlenecks in disk I/O at the file server and increase the
disk performance. It may be helpful to place the PROGRESS
database (.db file) on the file server. When this is done the
PROGRESS before-image (.bi file) should be stored on the database
engine to ensure database integrity. This can be done with the
PROGRESS before-image (-g) startup parameter.
4. Multi-Volume Database (DOS Server)
For databases which are 8 MB or larger, it will help performance
to convert a single volume database to a multi-volume database,
with each database extent being no more than 8 MB in size.
ONLINE PROCEDURES OR UTILITIES:
===============================
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
Environments Guide (PROGRESS Version 5) - Chapters on PROGRESS Startup
and Shutdown and Multi-Volume
System Administration Guide (PROGRESS Version 5) - Chapter on DOS/LAN
System Administration I: Environments (PROGRESS Version 6) - Chapter on
DOS/LAN
System Administration II: General (PROGRESS Version 6) - Chapter on
Startup Options and Multi-Volume
Novell Menu Utilities
Progress Software Technical Support Note # 1235