FinSQL.exe "eats" our precious memory?

fredefrede Member Posts: 80
Even though we have object cache set to 16 Mb. and we can monitor memory usage at startup of the client in the Task Manager to be approx. 15 Mb - then if we go to customer, open the overview (F5) and uses page-down, waits, presses page-down again, waits, presses page-down again, waits - and so on...

In Task Manager you can see finsql "eating up" memory - and not releasing it if you press ESC. If you press F5 again and does the same - but with page-up (showing the same records), finsql just keeps on "eating"...

It is not a problem on a stand-alone client - but on our Citrix Servers then each client can potentially take more than 100 Mb. (we've seen up to 140 Mb.)

Anybody knows anything about this - our IT organisation worries about this to potentially grow into a performance problem on Citrix.

Why is FinSQL not only caching 16 Mb.?
Why is FinSQL using up memory when we do a Page-down - and when we do a Page-Up it uses more (even though data just has been read)?

With the Native 3.70 client this is not a problem? It does not "eat" while using Page-up and Page-down.
We use Dynamics NAV 5.0 SP1 latest build 28412 (we installed this to see if the problem maybe was fixed with latest finsql.exe)
Regards,

Henrik Frederiksen, Denmark

Comments

  • kinekine Member Posts: 12,562
    NAV client have own data cache which is dynamic and NAV is adapting the size regarding free RAM. 100MB is common size of the client after while...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • krikikriki Member, Moderator Posts: 9,110
    And 5.0SP1 uses more memory than 3.70.
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!


  • fredefrede Member Posts: 80
    Thanx for the replies.

    After more testing our IT people have experienced that NAV "cleans" data cache at random times - so I guess you'r right - we should calculate with memory pr. client around 100 Mb.
    Regards,

    Henrik Frederiksen, Denmark
Sign In or Register to comment.