CppCon 2016: Chandler Carruth “High Performance Code 201: Hybrid Data Structures"

Channel:CppCon · Length:55:49 · Published:2016-10-01 · Views:119167

Watch on YouTube

Summary

Chandler Carruth's CppCon 2016 talk on designing hybrid data structures for performance. He covers cache locality, working-set size and allocation overhead, and why standard C++ containers fall short.

Why HN recommends it

Cited as the source for criticism of std::deque and move-constructor pitfalls, and as motivation to write custom data structures.

I suggest watching this talk — HN, 2021

C, C++, Rust, Go & systems languages · Software performance & optimization · Algorithms & data structures

Subtitles (excerpt)

All right. So, my name is Chandler Kut. I'm up here to talk to you about high performance code. How many folks are here at CBPCON for their very first time? Woo. Oh my goodness, that's a lot of people. Okay. So, how many folks have seen the the talk from two years ago on YouTube? Okay. Okay. That's that's better because I'm not going to repeat that talk. So, this is kind of the second of a series, right? The idea is that the first time I talked a lot about kind of things that that really limit high performance code kind of patterns you want to develop, fundamental things you want to do over and over again. But I felt bad about that talk for one reason. Uh one reason was that it was very negative, right? Like it wasn't actually a very constructive talk. I didn't tell you guys a lot of things you can do and you should do or kind of new and exciting tools to try and help you out writing really fast code. So this talk is going to try and be a little bit more a little bit more upbeat. It's going to try and help you guys out a little bit more. We're going to try and actually go through and and describe some hybrid data structures that uh are going to hopefully be very useful for you when writing really

On Hacker News

I suggest watching this talk: [VIDEO] Or pretty much any other by Chandler to understand why the STL sucks and why you should write better datastructures for your own use cases. — typon, 2021-08
in CppCon 2016: Chandler Carruth “High Performance Code 201: Hybrid Data Structures"[1] he says: "but the standard deque data type is really quite bad. I wouldn't recommend anyone use it for anything. if you look at the implementation constraints, the constraints placed upon its iterators, and its invalidation constraints, it's painted into a very unpleasant corner and it has very few opportuniti… — 04091948, 2020-04
The parent was asking the goldilocks question -- was there ever a point where C++ was not too complex like modern C++, e.g. this {} issue, but had enough features (contrast with C, which doesn't have enough features for many applications). I don't think there was such a moment. Apparently move constructors were a de-optimization in the case of std::vector. As far as I remember, it's related to it… — chubot, 2016-11

Related videos