Hi, from my understanding, if profiling is enabled then all modules of the engine will be profiled. In our use case, we create one engine and then submit serverless tasks to same engine. Is it feasible to profile only one module?
Currently, no, everything within one engine is profiled. That's not really a technical restriction though it's mostly just how it's designed. One thing you could do perhaps is to have two engines, but if that's not feasible then having more configuration settings seems reasonable to me!
@Alex Crichton It will be preferable to have a config option to profile individual module. Shall I create a github task for it?
Sure yeah, it'd be good to have an issue with detailed information on this
Last updated: Nov 22 2024 at 16:03 UTC