Slow posting of Sales Order on Navision Native database

Tan_Eng_Siong

Hi

I currently have a user who is complaining about the speed of posting sales order. They are Native database version 4.0. I have already increased the database size so that 70% is used.

The server is Intel Xeon Processor 3.0GHz/1M. 3.25 GB of RAM. Is there anything that I can do to improve database speed? What are things to do to improve sales order posting?

The items sold do not have lot\serial number and there is no expect cost posting.

Thanks

Tan Eng Siong

Marije_Brummel

Have you used the client monitor to see where the problem is?

kine

No info about Harddisks - they are often the bottleneck when posting...

ajhvdb

yes, but only with some elimination you can point a finger:
- Try it with the client on the server
- Try it with the client and the database opened locally
- Try it with a larger client cache
- etc.

Savatage

kine wrote:

No info about Harddisks - they are often the bottleneck when posting...

What's you disk setup?

# of disks
Size of disks
type of array
# of users
what's the size of these orders? 10 lines/100 lines/500 lines?

that kind of information

kriki

On the server:
- as DB-cache you should have about 10% for your DB in use (max 1 GB). It must also fit into the memory, if not it will be swapped to disk.
- you have the COMMIT-cache on)

On the client:
- you need some object-cache here. For 4.00, the standard is 32MB. This should be enough, if you don't have VERY BIG objects (=several MB) in the DB.
- you need enough memory on your client to have Navision NOT swapped to disk (probably is not the case)
- you need enough processing power on your client

The network:
- should be 100 Mbit or better and not too much conflicts.

The programs:
- don't have too many dimensions. This slows down.
- don't have too many indexes in the tables where something is written. This slows down.
- When you're posting, is there some message on the statusbar saying Navision is scanning a table. This means somewhere you are using a wrong index.
- If you are posting 1000 lines, it is logical it won't be done in 2 seconds.

Tan_Eng_Siong

Hi

The Harddisk is a single 70GB harddisk.

The number of users is 10.

The sales orders are all about 30 lines each. About 50 orders a day of such size. There are about 100 sales orders but they are strictly one or two lines.

As for testing it on the server\client, I could not detect any noticable difference. But I was testing at a off peak period. I strongly suspect that there are certain activities Navision that affects the sales posting performance.

Tested their data with the client monitor. There is no noticable bottleneck as compared to a fresh CRONUS database.(But as I stated above, it is was an off peak time.)

Will test the client cache and the DB cache. It is not likely to be an indexing issue as we have checked that already.

Thanks for the help.

kriki

Make also a form on table 2000000009:"Session".
Property TimerInterval=1000;
"Form - OnTimer()"-section : put the following code:

Currform.UPDATE(FALSE);

With this you monitor how much workload (cache reads, DB reads, DB writes) the different users put on the system.
Field "Sum Intervals" is interesting to know if the indexes are ok. If a session has a very hight number, it means in 1 (or more) of the objects the session is using, a wrong index is being used. In this case ask the user which programs he is using and check them out for wrong indexes.

Some other hints :
-don't use RAID5 for databases, but use RAID 1 or RAID10
-divide the database in different files, and put each file on different disks

ecclectic

Hi Tang Siong,

just wanted to know how u tackled the problem and is it going better.

thanks

Alex_Chow

What kind of RAID do you have?

Thanks to the people on this forum, I learned that RAID 5 gives the worst performance in an environment where there's a lot of writing.