Cold performance of ResourceManagerStringLocalizer is atrocious

[DamianEdwards]

Consider a localized version of the home page in the standard ASP.NET starter web template. You get around 50 localized strings. This results in 50 calls to ResourceManager.GetString that will throw MissingManifestResourceException when using the base language (i.e. one that doesn't have a specific culture assembly). That takes about 6 seconds. The next call is super fast as everything is then cached (~15ms).

Need to explore how we could possibly make that initial render faster.

[Eilon]

@DamianEdwards please round up some folks to come up with a plan for this.

[chemitaxis]

I have added a new issue, could be this in relationship with my issue? Thanks!

#252

[Eilon]

@ryanbrandenburg can you take a look to see where the time is being spent at startup?