Re:Introducing Atlas: Netflix's Primary Telemetry Platform
by dkhenry on Friday December 12, 2014 @02:38PM
(#8742233)
Sounds like a great platform. I wonder how many instances of everything they need for peak time. I have a system that is rated for 5M Time series data points per second and it takes about 150 physical servers so I am curious about what a Netflix sized ( 20M time series data points per second ) would look like.
[ Parent
| on HN ]
Re:Introducing Atlas: Netflix's Primary Telemetry Platform
by CrankyFool on Friday December 12, 2014 @05:11PM
(#8743025)
"It's complicated."
As the announcement notes, we have multiple tiers holding different data horizons. The most active, and large, tier is the one holding the last six hours of data. That tier, being the most critical one (we try to train our engineers to only need 6 hours of data to understand how their system is working in the worst case), is mirrored. Right now, each of those mirrors is about[0] 756 r3.2xl instances.
[0] For a very exact definition of "about," though that exact number could change in the next 5 minutes, or 5 hours, or 5 days, or not until we see another metrics increase.
Re:Introducing Atlas: Netflix's Primary Telemetry Platform
by Thaxll on Friday December 12, 2014 @04:54PM
(#8742944)
In the video they say that they're close to 1B/min.
http://youtu.be/tHrT6kQR7vw?t=36m
Re:Introducing Atlas: Netflix's Primary Telemetry Platform
by CrankyFool on Friday December 12, 2014 @05:12PM
(#8743031)
Pshaw. That was last year :)
(The presenter in the video)