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. Range of required resources

Range of required resources

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 47.1k 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.
  • F
    F
    fabrizio.alba
    wrote on last edited by
    #1

    Good morning everyone!
    As final work for my degree thesis, I am bringing the report on the implementation and configuration of netXMS in my Company network.

    Dear Admins, based on your experience would you be able to evaluate the necessary resources (CPU, RAM, DB disk space) depending on the number of clients to monitor, excluding the space required by Windows logs?
    Something like:
    from 1 to 100 clients: x CPU, yGB RAM, z GB DB space
    from 101 to 500 clients: ...

    Thank you so much for your support and the wonderful product you have developed and supported.

    Fabrizio

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

      It's quite hard to estimate required resources, as they depend not only on the number of nodes, but also on number of interfaces, number of DCIs per node, data collection interval and storage time, number of scripts, number of various events happening and so on. Also, on big systems use of Timescale DB helps, as it minimizes housekeeper resource usage.

      Here are some real-life data about tree installations - X, Y and Z. All are using SSD or NVMe storage. On these systems Postgres (non-timescale) was used, running on the same server, so RAM and core numbers cover both NetXMS and DB engine.

      Number of datapoints per second was obtained from the DB by this query: SELECT polling_interval, retention_time, count(polling_interval) FROM items GROUP BY polling_interval, retention_time ORDER BY retention_time, polling_interval;
       

      X Y Z
      Objects 20554 56040 41542
      Monitored nodes 2175 2656 5376
      Collectible DCIs 34260 185742 372240
      Collected datapoints per second 372 979 2290
      Stored datapoints, millions 8995 14978 44195
      RAM, GB 24 74 160
      CPU cores 8 10 20
      DB size, GB 237 1500 1500
      Bytes per datapoint 53 108 61
      1 Reply Last reply
      0
      • F
        F
        fabrizio.alba
        wrote on last edited by
        #3

        Thanks Filipp!
        Very helpful as usual...  🙂
         
        Fabrizio

        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