Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • YouTube Videos
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
      • Learn more about Agile
        • Agile Webspace
        • Everything Agile
          • The Agile Manifesto
          • Best Practices
          • Retro Recipes
        • Methodologies
          • The Scrum Framework
          • Kanban
          • Extreme Programming
        • Roles
          • The Product Owner
          • The Agile Coach
          • The Quality & UX Coach (QX)
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Pogram
    • DataMiner DevOps Support
    • Feature Suggestions
  • Swag Shop
  • Downloads
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Solutions
    • Deal Registration
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

Expected unavailability of elements when swarming

Solved342 views26th June 2025swarming
0
Edson Alfaro [SLC] [DevOps Advocate]1.39K 10th February 2025 0 Comments

Hi all,

Exploring the new swarming feature, is any way to get a metric of how long the elements will be unavailable during the process?
Swarming | DataMiner Docs

Is it possible to make any estimations?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 26th June 2025

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
0
Marieke Goethals [SLC] [DevOps Catalyst]5.94K Posted 11th February 2025 2 Comments

Hi Edson,

Some metrics are available for this on docs: https://docs.dataminer.services/user-guide/Reference/Metrics/swarming_elements_benchmarks.html

Is this what you were looking for?

Wouter Demuynck [SLC] [DevOps Advocate] Posted new comment 11th February 2025
Bert Vandenberghe [SLC] [DevOps Enabler] commented 11th February 2025

Let me try to translate those metrics into human readable language:

The swarm action itself, of one element, takes less than 200 ms (154 ms). But then the element still needs to perform its regular startup, and that depends on the connector. Most connectors start within a few seconds. Then it might take some more time before all the data is retrieved again, you have to take that into account as well!

Now, if you swarm 100 elements in one go, then it depends on how many DMAs you swarm them to. Each DMA can handle 10 elements concurrently. So if you swarm 100 elements to 1 DMA, then it will take 10 times the time it times for 1 element. Assuming one element takes 2 seconds, that would be 20 seconds in total. If you have 2 DMAs handling those 100 elements, then you would only need 10 seconds.

In other words, in a swarming world, you want more DMAs and less elements per DMA in order to make your system more resilient.

PS: Not sure if my human readable language is that human readable after all 😉

Wouter Demuynck [SLC] [DevOps Advocate] commented 11th February 2025

It's maybe also useful to compare swarming time to element restart time, because a swarming action is basically an element restart with some extra overhead in transferring control. If an element takes a long time to restart, it will also take a long time to swarm.

Swarming one element would take about as much time as restarting one element.

The time for swarming multiple elements at once depends on how those elements get spread across multiple agents (more destination agents => faster availability). Even when swarming to one destination agent there is a certain degree of parallelism when starting up elements after the swarm.

You are viewing 1 out of 2 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin