Arev Speed under NT (Third time posted) (AREV Specific)
At 26 JUL 1998 12:56:52PM Christopher Helten wrote:
TO REVSOFT: On two prior ocassions you have not responded to the questions I have listed here. I would appreciate a response to get your perspective on this issue. Below are questions I have posted two other times prior. I have had responses (Not Revsoft), of which I appreciate, however they did not answer the questions below.
I am looking for the suggested configuration settings to acquire optimal performance in the environment listed below. I am sure Revsoft has taken the time to document what it feels to be the correct configurations for different environments.
I am running the following configuration:
Window NT 4.0 Server Pentium 166 (128 meg RAM) - using NT Service (version 1.5)
Window 95 workstations (25) using NPP
TCP/IP protocol only
Currently, like many other NT users we have experienced intermittant slowness. This usually occurs when report process has been started and the initial index select process is completed and the reduce process has begun, however there are times when only one user is on the system and still experiences the same problem.
I have reviewed several of the responses to this topic but still have not really seen an answer. According to Revelation what is the proper or suggested configuration to resolve this issue or can this issue be resolved? I realize that Novell is one answer, but that is not an option for me at this point.
1) What type of partition should Arev be running on NTFS or FAT?
2) How much memory is suggested for the server? workstations?
3) What protocol is suggested or required (TCP/IP, IPX, Netbeui)?
4) Does Revsoft have a complete configuration listing for many of the most pertinant settings?
At 26 JUL 1998 04:25PM Curt Putnam wrote:
Another response from a non-RTI person.
FWIW, I've seen Arev run on 2 different NT networks now. Arev, running under Win95/98 is real happy as long as you can give it enough expanded memory.
NT servers have (in my sample of 2 ) caused all kinds of problems, usually because they are application servers rather than being configured as file servers. I've seen the networks simply halt for 10 - 20 seconds while the server catches up.
I'm not sure there is a useful response - it's just the way NT is.
At 04 AUG 1998 02:00AM Larry Wilson TARDIS Systems, Inc. wrote:
First, ALWAYS configure your main NT server as a PDC, never peer-to-peer.
Second, TCP/IP as primary? Nyet. NetBuei ONLY unless you are doing WANs or Internet nets, such as with PPTP.
The Win95s should ALWAYS be configured, under the PERFORMANCE tab, as network servers (give them more files handles).
Any problems, e-mail at: tardis@earthlink.net.
At 04 AUG 1998 04:18AM Andrew P McAuley wrote:
This is a public forum and RevSoft do not specifically say that they will answer here. They specifically say that they will answer in the Works forum - i.e. those who are paying for support. Failing that a paid customer support call is also guaranteed an answer.
I know that this is not a helpful response but your message seems to indicate a disappointment that you were not answered directly and this just tries to suggest a possible reason why.
You're probably as well off listening to the non-RevSoft responses as they are from people who are actually USING the product in anger. Larry and Curt are both very well respected in this regard.