We use dynamic_cast in many places under db/pipeline to determine whether a pipeline stage is of a certain type and in some cases invoke methods on the DocumentSource subclass instance returned. Several locations show up as a hotspot under VTune when running the "Aggregation.Lookup" mongo-perf micro-benchmark. We should look to replace dynamic_cast usage with a more performant mechanism.