Performance issue when web.config is really huge

Does it have any major effect on performance/ memory if my开发者_运维知识库 web.config is really huge (say, 1000+ entries in <appSettings>)? Is it a good idea to maintain a different custom xml config file for all business specific settings for my app? Thanks.

This could potentially delay application startup slightly, but since all settings will be read from memory after that, it shouldn't have any performance impact.

The web.config file is usually just read once and the info cached so I dont think it will have any performance issue.

ASP.NET: Where/how is web.config cached?

Yes it does.Web app config file works when your page load at the first time.So when ever your application is loads the Web app is read and loaded in the memory.So this will create performance issue on your application and better to put non application level settings on xml file.