System.Data.SQLite

While profiling our application I see that we spend a surprising amount of execution time in UnsafeNativeMethods.GetSettingValue. It is even worse if we actually have an xml config file, looks like the xml file is read and parsed every time GetSettingValue is called. 

Perhaps this information could be determined only once and cached instead? Preferably in a way that enables lock free reads. 

I see it primarily when creating new instances of SQLiteConnection and in SQLiteConnection.Open. Open is twice as bad as SQLiteConnection.ctor since it redoes the work twice, once by calling ParseConnectionString and once by calling get_DefaultFlags.

This looks like a duplicate of [58ed318f2fadb5e0feff], which was fixed.

The frequently used settings are cached on a per-connection basis.

Access to the DefaultFlags setting can be disabled using NoDefaultFlags in the
connection string.

Access to the No_SQLiteConnectionNewParser setting can be disabled by setting
the ParseViaFramework property of the connection prior to calling Open();
however, this may be problematic because the alternative connection string
parsing algorithm exposed by the .NET Framework may not be entirely compatible.

I've attempted to improve this situation with check-in [7d50138407b6992b], now
on trunk.

Could you please test these changes in your environment and tell us if they
improve the performance for your use case?

Your changes improves things a little bit. 

Hadn't noticed No_SQLiteXmlConfigFile before, setting that makes the biggest difference. Sorry about that.