Which one is more performant in NestJS: adding a class instance in context or using @Injectable(scope:scope.REQUEST)

Question

To implement Dataloader in NestJS application with GraphQl, to avoid caching, we need to limit the created dataloader instance to every single request. Can you guys help me have better understaning of differences between this two approach: adding an instance of it in context or using @Injectable(scope:scope.REQUEST)?

Both approach should lead to the same result.