Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Slow load time for NetXms

Slow load time for NetXms

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 22.5k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E
    E
    Egert143
    wrote on last edited by
    #1

    Hello

    How can i debug why NetXms Management Console is starting up really slow? Currently timed startup time to 3min and 53s. Most of that time was spent on "Synchronizing objects...".

    Version is 3.8.382
    DB is Ms Sql 2019

    Show dbstats:

    Total: 2183360433
    Select: 470887177
    Non-Select: 1712735689
    Long running: 0
    Failed: 0
    Background writer requests
    DCI data: 552603253
    DCI raw data: 622931142
    Others: 1633579
    

    Show stats:

    Objects: 38264
    Monitored nodes: 5644
    Collectible DCIs: 16531
    Active alarms: 642
    Uptime: 52 days, 0:37:07
    

    Show syncer:

    Last run at 15.Oct.2021 09:45:28
    Last run time: 4077 ms
    Average run time: 3496 ms
    Max run time: 106385 ms
    Min run time: 1015 ms
    
    1 Reply Last reply
    0
    • F
      F
      Filipp Sudanov
      wrote on last edited by
      #2

      Was is faster of previous versions? What is the network throughput and ping time between nxmc machine and the server?

      1 Reply Last reply
      0
      • E
        E
        Egert143
        wrote on last edited by
        #3

        It seems to have gotten slower with addition of new nodes over time.

        Server is in same machine as sql. Client is connected with 1g link and ping time is ~1ms.

        It seems restarting the server + changing "ThreadPool.Poller.MaxSize" from 250->1200, "ThreadPool.Poller.BaseSize" 10->600 helped, now it loads in few seconds.

        1 Reply Last reply
        0
        • F
          F
          Filipp Sudanov
          wrote on last edited by
          #4

          That's a great finding. The reason is that pollers can lock objects in some situations. Increasing the number of pollers reduces the chance that a locked objects would be encountered when nxmc is syncing objects.

          1 Reply Last reply
          0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          Powered by NodeBB Contributors
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups