Performance slows down by 4 times (AREV Specific)
At 21 OCT 1997 05:58:19PM Dave Bennett wrote:
Whole system slows down by 4 times at all stations during different times of the day. The system is as follows.Arev 3.111
NLM 1.1
Novell 3.12
20 users
all Dos minus 2 Win95 pc
indexer installed
Server P150 32Meg 1Gig Duplex drives
Server rebooted every Sunday and within 48 hours had 10.5 million packets sent
Any help would be appreciated
At 21 OCT 1997 06:14PM Aaron Kaplan wrote:
Slowed down how? All together? Sporadically? Is there a specific time during the day, like 3:30 or after marketing gets back from lunch or when accounting does the vacuuming?
Which TSR are you using? What are the workstation settings?
Is there anything on the server besides ARev? If so, what is it?
At 21 OCT 1997 08:52PM Brock Prusha wrote:
A couple of ideas:
1) There's a whosawhatisit setting on the Novell Server.
It's something like the Amount of time to wait before
flushing write befores. Set it to 1. Performace for your
Arev Ap will improve but disk i/io will go through the
roof.
2) In the NLM settings, make sure the frame size is
set to whatever the frame size is on your network.
3) For Arev, you can define the temporary sort file
to a local drive. This can be done from Sysprog and be
set for each workstation using an INI file. Set the
sort file to something like C:\Temp. Someone could be
doing large selects (thats why it's sporadic) which
could drag on network resources.
Brock Prusha
DFM Systems, Inc
At 23 OCT 1997 05:06PM Locat Temp file wrote:
What happens if the local sort file does not exist or the disk goes full?
At 23 OCT 1997 10:29PM Brock Prusha wrote:
Well, the Arev determines the name of the actual
sort file. However, in answer to your questions:
1) If the file (or directory) does not exist, I believe
a black box message appears telling you so. This may
actually appear when you login. I haven't ran into this
in a while so my memory is flogged.
2) If it runs out of space, well, I think Arev generates
some weird error which does not come to mind. It might
actually say volume out of space.
Remember, an INI file can be setup so this setting
is workstation dependent. The thing that works best
for our clients is setting it to C:\ and not worrying
about it since harddrives tend to be pretty large these days.
Brock Prusha
DFM Systems, Inc
At 27 OCT 1997 11:13AM Bo Follaug wrote:
Hi Dave
We had almost the same problem, so we upgraded the NLM client from 1.10 to 1.12 and it solved the problem.
Bo Follaug </QUOTE> View this thread on the forum...