I'm working on a code base that has a lot of identical ConfigurationManager.AppSetting calls scattered throughout.

Does this sound like a possible performance issue?

Or because the data being very small is trivial and not 'expensive'? Constantly going back to the file to get the data, or does the .NET runtime cache the file/values/calls?

If this isn't a performance issue is it just a disorganized approach to accessing the application configuration values, and should just be re-factored to be cleaner and consistent implementation of accessing the settings?

.net performance appsettings
Edit
Report