Scalability. By Alex Huang. Current Status. 10k resources managed per management server node Scales out horizontally (must disable stats collector) Real production deployment of tens of thousands of resources
PowerPoint Slideshow about ' Scalability' - chip
An Image/Link below is provided (as is) to download presentation
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Fires off 10k requests every 5 minutes or 33 requests a second.
Bad but not too bad: Occupies 33 threads every second.
But just wait:
2 management servers: 66 requests
3 management servers: 99 requests
It gets worse as # of management servers increase because it did not auto-balance across management servers
Oh but it gets worse still: Because the 10k hosts is now spread across 3 management servers. While it’s 99 requests generated, the number of threads involved is three-fold because requests need to be routed to the right management server.
It keeps the management server at 20% busy even at no load from incoming requests
Fires off 1 request at resource connection to sync about 50 VMs
Then, push from resource as resource knows what it has pushed before and only pushes changes that are out-of-band.
So essentially no threads occupied for a much larger data set.