Slow access on Upgrade to 4.0

Ade_Aluko

My client's experience is very discouraging on upgrade to 4.0

The clients run too slowly to be desired. Any idea what could be wrong as we are considering reverting back to 3.7?

We run a database size of 36GB

Thanks.

Ade Aluko

kine

Please, more info:

DB type : MS SQL or Native
DB Files: One? More? RAID? More physical RAID volumes???
DB Server RAM size?
DB Server CPU?

Client RAM?
Client CPU?

Network?

Is there some remote access?

Ade_Aluko

Native Database
RAM 4.0

No remote access

Conversely, I converted a 3.7 database to 4.0 (no changes was made), but the experience is still the same. It's slow compared with when the same database was running on 3.7. The search time is longer even when nothing has changed (any compatibility issue).

Thanks

Foxman

Ade Aluko wrote:

My client's experience is very discouraging on upgrade to 4.0

The clients run too slowly to be desired. Any idea what could be wrong as we are considering reverting back to 3.7?

We run a database size of 36GB

Thanks.

Ade Aluko

---

Follow Navsions basic rule:
1. Have good hardware, Multiple diskdrives to increase the IO read/write.
2. Make sure the server is running about 700mb of RAM in the services.
3. Make sure the network traffic is good, 100mb nic cards.
4. Where is it slow; reports, posting, searching.
a. Reports, make sure the correct keys are used.
b. Posting s/a.
c. Searching, if the user is filtering, make sure they know which keys to activate when performing a filter.
d. Test the database on a local PC to see if the slowness still exist.
e. Try purging a lot of history outthere! Don't settle from the client 'We need all the data, we need it because..... That is not the correct answer.
f. Purging Item Ledger entries, delete records that no longer required, Deleting customer ledger etc.. :-k

Geovanny

Ade_Aluko

Thanks.

I've checked all these. They won't agree to delete any entry.

However, my concern is the fact that it's not the same experience with 3.7, with same configuration and database.

Any requirements disparity between 4.0 and 3.7 that can be responsible for this?

Regards.

kine

May be some "optimization" on Native server to show that MS SQL is faster... :-)

I think that 4.00 is less optimized than 3.70 by design. Do not forget, that it is first version released (if you are not using Update 1) and it is not stable. And one big change: default of Object case on client is now 32MB...

Ade_Aluko

Thanks.

I've checked all these. They won't agree to delete any entry.

However, my concern is the fact that it's not the same experience with 3.7, with same configuration and database.

Any requirements disparity between 4.0 and 3.7 that can be responsible for this?

Regards.

kriki

You might also have to change the maintaining of indexes and SIFTIndex on SQL.
Check out my reply with example in http://www.mibuso.com/forum/viewtopic.php?t=7235