DbSet.Find method ridiculously slow compared to .SingleOrDefault on ID

Find calls DetectChanges internally, SingleOrDefault (or generally any query) doesn’t. DetectChanges is an expensive operation, so that’s the reason why Find is slower (but it might become faster if the entity is already loaded into the context because Find would not run a query but just return the loaded entity).

If you want to use Find for a lot of entities – in a loop for example – you can disable automatic change detection like so (can’t write it in VB, so a C# example):

    context.Configuration.AutoDetectChangesEnabled = false;
    foreach (var id in someIdCollection)
        var competitor = context.Competitors.Find(id);
        // ...
    context.Configuration.AutoDetectChangesEnabled = true;

Now, Find won’t call DetectChanges with every call and it should be as fast as SingleOrDefault (and faster if the entity is already attached to the context).

Automatic change detection is a complex and somewhat mysterious subject. A great detailed discussion can be found in this four-part series:

(Link to part 1, the links to parts 2, 3 and 4 are at the beginning of that article)


Leave a Comment