Unfortunately the talk was not recorded. There is no transcript either.
If people will have a lot of questions about slides (there is nothing novel there though) I can do a follow up post.
Might be a lot to ask, depending on the time needed to write a couple of lines - but I guess right now it's most helpful for the people that are already educated on v8 performance.
It's just that you could easily educate a broader audience (cough - like the author here) with a short write up. Some things are 'obvious' (GC pressure), some (everything about 'In hot code', some of the trace parameters) things are opaque and ~meaningless~.
I wondered too if they had more to say about the usefulness of some of the trace parameters. I am pretty sure they refer to what the profiler traces (and logs), but I don't know whether they got any usefulness out of them.
What I meant was: The whole 'in hot code' part of the slides didn't make sense to me, because it's something like a list of (unexplained) statements. I know what 'hot code' refers to, I just don't particularly like to accept things as facts without a minimum of explanation. Probably the author is dead on and I'm sure he knows a lot more about the technology than I do, but 'don't use X, use Y' or 'avoid Z' is something that should be qualified.
Probably the talk did that.
Trace parameters are there to give actual nodejs/v8 users a chance to experiment, to trace their app and see what optimizing compiler does to their code.