With the number of jscore passthroughs, patches that modify even just a few tests in jstests/core/ can generate a lot of burn-in tasks. It's frequent that this even exceeds Evergreen's task generation limits.

This ticket should be used to investigate possible smarter strategies for burn-in generation.

Thoughts off the top of my head:

• Use some sort of "budget" for a maximum of how much burn-in to generate
• Revitalize the "covered by more complex suite" concept. See https://github.com/10gen/mongo/blob/126b045a21edf2005939498ccb5bcc468b048bfa/buildscripts/resmokelib/suite_hierarchy.py