SaveChanges() overhead

When calling DbContext.SaveChanges(), is there any performance benefit to checking whether there are any changes to be saved? For example:

if (context.ChangeTracker.HasChanges())
    context.SaveChanges()

Or is this the kind of check that EF is performing internally when SaveChanges() is called?