mibuso.com
Home› NAV/Navision Classic Client

OBject Cache in NAS

TatoshkaTatoshka Member Posts: 17
edited 2014-02-08 in NAV/Navision Classic Client
Please help me
We use NAS for Job scheduling, and now the size of Object Cache is 64000KB. We have slowness of transaction the users cannot login sometime and so on.
Advice what should be done. Can I delete Job log entries and will it help to increase the speed of transaction. Should I reduce Object cache size? as I know max is 1GB?

Thanks

Comments

  • vaprogvaprog Member Posts: 1,141
    How's the NAS's performance as compared to a regular client? I.e. does it take the NAS longer to post a document than a GUI client for example?

    It is unlikely that the performance bottleneck is in Object Cache, especially not with a cache of 64000KB for the NAS, which does not use any GUI related objects.
  • TatoshkaTatoshka Member Posts: 17
    Since the jobs can run during user transcations they can lock same tables. But my question is related to Objects Cashe is it ok 64000KB? how should I set that parmeter. What is the best size ofr it?
    and Is the Job entries log size can affect on job performance?
  • bbrownbbrown Member Posts: 3,268
    A 64000KB Object Cache is excessive. It should be no higher, possibly less, than you would have your classic cleints set. After all, that's what NAS is. A classic client without a screen. Having this so high could be limiting memory for other process and contributing to performance. But likely not the whole cause.

    Deleting records from that table is likely not going to help.
    There are no bugs - only undocumented features.
  • TatoshkaTatoshka Member Posts: 17
    thanks for reply
  • kapamaroukapamarou Member Posts: 1,152
    I haven't had issues with this. I use 32000 Kb but it depends on what is executed through NAS. I bet your issues are elsewhere. However, you can monitor how often NAS accesses the object table.
    In your place I would start by using client monitor or SQL profiler to identify bottlenecks.
  • bbrownbbrown Member Posts: 3,268
    Start by taking NAS out of the picture. How does the process behave if run from the classic client? If it is a performance issue with the process, will be much easier to debug/troubleshoot as a client process. Then you can move it back to NAS.
    There are no bugs - only undocumented features.
  • einsTeIn.NETeinsTeIn.NET Member Posts: 1,050
    We never changed the standard value of Object Cache of NAS and we have one process also based on Job Queue where a huge amount of objects is involved. And we never had performace issues like you describe.

    Btw, what do you mean by "the users cannot login sometime"? Is there anything that is create by NAS that is also create during login?
    "Money is likewise the greatest chance and the greatest scourge of mankind."
  • TatoshkaTatoshka Member Posts: 17
    einsTeIn.NET the Login issue has been resolved. It is no related with object cache,
    It was SQL Server issue.
Sign In or Register to comment.