Performance issue in Native database (10min to login)

wfmunwfmun Member Posts: 19
Hi all, my customer is using Navision 3.70 with Native database. The database size is about 6GB, number of concurrent users is 11.

Everyday, the first user to login Navision has to wait for about 10 minutes to start up navision. All subsequent logins take only a few seconds.

Does anyone face the same problem before?

Could it be the below causes?

1) Server Hard disk space (40GB of hard disk free space, 32GB of used hard disk space)

2) Using native server instead of SQL Server

3) Server RAM (Available memory modules in total is 1536 MB)
Or other reasons?

Comments

  • Luc_VanDyckLuc_VanDyck Member, Moderator, Administrator Posts: 3,633
    It's normal. When the first user logs in, the Navision cache is filled with data. If you have setup a large cache on the server, this can take a while.
    No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)
  • kinekine Member Posts: 12,562
    Or problem can be antivirus SW checking the DB files.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • themavethemave Member Posts: 1,058
    It should only be doing this if you are stopping the service at night. It goes through a recovery of free disk blocks the first time a user logs on after the service has been stopped.

    Are you stopping the service each evening for backups. you can run Navision Backup without stopping the server service.
  • kinekine Member Posts: 12,562
    themave wrote:
    It should only be doing this if you are stopping the service at night. It goes through a recovery of free disk blocks the first time a user logs on after the service has been stopped.

    Are you stopping the service each evening for backups. you can run Navision Backup without stopping the server service.

    It is not needed to stop the service. After last user is diconnected, the DB file is closed. During first user login, the file must be reopened -and in this case antivirus can check the file etc.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • wfmunwfmun Member Posts: 19
    It's normal. When the first user logs in, the Navision cache is filled with data. If you have setup a large cache on the server, this can take a while.

    Refering to the database information, DMBS cache and object cache are default to 8000KB. It is consider a large cache? :-s

    themave, no. The user does not stop the service each evening for backups.

    Kine, thanks. If antivirus is a cause, can we do anything to maximize the performance? Such as , schedule the scanning before first user login...etc?
  • kinekine Member Posts: 12,562
    No, you can exclude the fdb files from the scan. But it depends on which antivirus you are using.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Luc_VanDyckLuc_VanDyck Member, Moderator, Administrator Posts: 3,633
    wfmun wrote:
    Refering to the database information, DMBS cache and object cache are default to 8000KB. It is consider a large cache? :-s
    I think you are looking at the cache settings of the client instead of the server, as there is no object cache on the server.
    No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)
  • wfmunwfmun Member Posts: 19
    I think you are looking at the cache settings of the client instead of the server, as there is no object cache on the server.

    Yup, sorry. The actual server DBMS cache is 1GB which is the maximum value one can set. If this is the cause, user has to live with it, or to reduce the size of the DBMS cache (which will affect program speed when program is running)??

    For some of your benefits who may view this log, the recommended DBMS cache is :-
    +amount of Physical Memory
    - memory requirement of the operation system
    - 50KB * no. of workstations
    - 1M for the Navision server
    - memory requirements of other programs

    By the way, when my customer tried logging in using IPAddress instead of servername, the waiting time reduced by 80%! So i think it is considered solved! \:D/
    Thank you guys!
Sign In or Register to comment.