AREV 3.0 running very slow ... (AREV Specific)
At 17 APR 2000 04:04:45PM Damon wrote:
I am running AREV 3.0 on a Windows NT 4.0 server with Win98 client PC's and things are much slower than when on a Novell Server. I have installed the NT Service and NPP. I have tried everything in the NT Service FAQ. I would like to try to have a seperate workstation doing all of the indexing, but I am not sure how. Can anyone help? Thanks
At 17 APR 2000 06:33PM Paul D'Amico wrote:
We have had success improving AREV's behaviour under NT 4.0 with Steve Smith's CPU-PLUS utility.
Paul
At 17 APR 2000 07:21PM Warren wrote:
Indexing Station:
Just setup one user name with background indexing and all others in the same application not to have background indexing. The settings are in the environment and can be set from SYSPROG.
Make sure the indexing user attaches all the same volumes as the rest.
After that it is a matter of tweaking the time between index updates and whether or not the users should update indexes on queries (usually best to turn this off first).
At 18 APR 2000 09:20AM Stephen S. Revelation wrote:
Damon,
Here are some tips that we give to customers having slowdowns caused by the NT Service. The content posted below will provide the basis for an upcoming KB article.
Here are some tips to speed up the NT Service.
It is important that the server be up when the workstations reboot, and that the workstations are not logged into the server at the time of reboot.
1a)
If you have a DOS FAT formatted hardrive:
Check the "files= parameter in all workstations config.sys files.The number of files should be over 100.Try using "files=101".1b)
If you have a Windows NT NTFS formatted hardrive:
Check the "files= parameter in all workstations config.NT files.The number of files should be over 100.Try using "files=101".2)
Log out all users and stop the service (lhsrvc stop).
Remove the service (lhsrvc remove).
Recreate the service (lhsrvc create).
3)
Unmap all of the workstations from the server.
4)
Reboot the server.
5)
Reboot the workstations.
6)
Remap the workstations to the server.
7)
Launch your application.
This usually will fix most of the NT server slowdowns.