Should Domain login have any performance impact?

pdj

(Using Navision 3.70 native, tcp/ip with db login)

I have a customer with multiple Windows domains. Now the customer complains that the performance in Navision is dependent upon whether or not the user is logged on to the same domain as the Navision server.

I have done a bit of testing at my office and I tend to agree. Our development server is configured to store NetTest result for each login, so I have a lot of reference data being on the domain. I then tried to login to my computer locally (this computer) a few times and compared the results. (We only have a single domain, so I’m unable to test the effect of using a different domain)

Logged on the domain: (60 tests)
Avg.:    4039   945
Min:     3496   389
Max:     4099  1260

Logged on locally: (8 tests)
Avg.:    3351   827
Min:     2732   733
Max:     3920   910

Difference (pct.)
Avg.:      17    12
Min:       22   -88
Max:        4    28

(If there is any difference in net load and/or server load, then the tests made locally was made in a very quiet time since I was almost alone in the office)

Has anyone experienced similar behavior? Or even better: Has a solution?
(Besides requiring all users to be on the same domain :-))

Edit: I just did some "ping -l 64000 <server>" and there were no difference between the two "modes" - they all gave 11ms with a few exceptions.

Captain_DX4

We had one user from a different domain logging into our native Navision database using Windows login. She was neither a regular user nor familiar with Navision, so she could have been unaware of performance issues, but I never got any feedback that her connection was anything less than any other logins on our network.

pdj

Ok, but our users are executing a lot batch jobs (Calculate Plan, Carry out action message, and some "home made" jobs). A lot of them lock a lot of tables, and it is quite frustrating they are locked more than they need just because the user isn't on the domain.

kine

If you have locking problems, you need to know:

1) How the clients are conencted? (which connection is used between the domains?)
2) Are they using good hardware on their PCs?
3) Are the jobs using good keys?
4) What is doing the server during the locks? Is there some HW bottleneck (discs, memory, CPU)
5) If the server is "sleeping" during the locks, the problem is elsewhere - network bottleneck, enduser PC, wrong keys...

pdj

Hi Kine,
Yes, we have already done a lot of optimization using the client monitor tool and a lot of homemade tools. But when the same physical computer with the same physical connection to the LAN experience a poor Navision performance, just depending on which domain the user logs into, then it is kinda out of our hands.
Is anyone able to either confirm or reject my findings?
I'm currently setting up at test enviroment with multiple domain, so I will be back with more detailed results.

kine

Because the PC is connecting into another domain, he can have IP from another subnet. This subnet can go through another switches etc... check this...

kriki

That reminds me something years ago (even before my Navision-time).
We had the same problem. When a user on another subnet connected to the DB, it went very slow.
This was because the connection between the 2 subnets was slow and all trafic between the 2 subnets went trough that slow connection. Once they fixed this, it went nicely.