The application settings mechanism (derived from ApplicationSettingsBase) seems to be a real bottleneck when used in multithreading scenarios. Especially, when properties are queried often, the concurrency they introduce is slowing down my loops. I like to use them anyway to have those nice application configuration option. But maybe I need to wrap them into my own cache or so?
Anyone having the same issue? Am I missing something? I thought, the ApplicationSettingsBase does cache all settings already? Why does it seem to lock access from multiple threads at all? What could be a common workaround?
I dont see annything strange in having a thread safe settings mechanismm? If it is slowing your hihgly concurrent theads down, you should try to use local variables istead of querying the getsetting fast again. I think a redesign of your settings request mechanism would help performmance considerably.