Performance Tipping Point: Hitting Hardware Bottlenecks - Akira Kurogane

June 29, 2017

Akira Kurogane, Senior Technical Services Engineer, MongoDB 

One week your active dataset consumes 90% of available RAM. The next week it's 110%. Is that a 10% or 99% performance degradation? Let's discover what it looks like when different hardware capacity limitations are hit. For example, memory vs. disk bottlenecks, the rare CPU bottleneck and network bottlenecks, seeing what happens when you drop a crucial index during peak load, or what happens when you run multiple WiredTiger nodes on the same server without limiting their cache size.

 

 

Previous Video
Building the Real-Time Performance Panel - Jonathan Balsano
Building the Real-Time Performance Panel - Jonathan Balsano

Next Video
Experience MongoDB World 2017 Montage
Experience MongoDB World 2017 Montage