Nf2.60 Server: Slow Performance

leugim

hi all

we have a customer running NF2.60 C server
cache = 4000Kb
commitcache = no
nettype = tcp

the machine is so recent (core 2 duo, memory enough and so on...) so we discard any computer problem

scenario: user A is posting a BOM Journal, user B is changing the Posting date in a Purchase invoice. when user A posts Bom Journal, the user B get a very slow performance and it takes too many seconds to change from one field to another. we have recreate this scenario "at home" and works fine

maybe the NF2.60 version?? server is mounted on C version, will it be better to mount server from F version?

had anyone of you have problems with NF2.60 performance??

regards

kine

1) just cache = 4000Kb ? it means cache 4MB - :-D change that to 600MB (600000KB) as minimum. (but I do not know now which maximum had NF2.60).

2) You didn't wrote anything about the disk subsystem - can you give us some info about your HDDs?

kriki

kine wrote:

1) just cache = 4000Kb ? it means cache 4MB - :-D change that to 600MB (600000KB) as minimum. (but I do not know now which maximum had NF2.60).

2) You didn't wrote anything about the disk subsystem - can you give us some info about your HDDs?

1) NF2.60 has the same limit as 4.00 : 1 GB in theory. In reality it is more like 800MB. So you can change your cache to max +-800MB. But remember to keep some free memory for the server itself. If you have over 1GB of memory, it should not be a problem. If you have only 1GB, check how much memory you are using without the Navision DB. Add to that 100MB and subtract this from the total server memory.
Eg.:Physical memory = 1GB
-In use (without the Navision DB):200MB.
-Add 100MB to the 200 MB = 300 MB
-1GB=1000MB - 300 MB = 700MB. You Navision DBchache should not exceed 700MB.
Put also the commitcache to Yes. This will speed up writing a lot. Best have a battery backup in case of a blackout.

2) disks : best use multiple RAID1-drives with on each drive a databasefile (up to 16: http://mibuso.com/blogs/kriki/2008/01/04/maximum-size-for-navision-dbs/). The databasefiles should be equal in size. The disks should be dedicated to the Navision DB (no other files on it!). Best use 15000RPM-disks.

Network should at least be 100MB. You client should have a fast connection to the DB (NOT via VPN over the internet or a telephone cable).

Remember that ALL processing of data is done on the client => don't use a 486-computer to do the posting. Use a recent computer.