v9 ideas

[valdisiljuconoks]

Echo from community:

• Change TypeFactory to regular dependency injection. It seems to allocate too much memory.
• Optimize ResourceKeyBuilder further.
• Consider replacing the queries with regular service class methods. They are not particularly slow. But the creation of them seems slow.
• Store the result of GetAllResources as a dictionary, so it is cached like that, as it is much faster to pull specific resources by name this way.
• It could also be nice to look into the data layer, like test the performance of loading from SQL Server, and the caching of data.
• enable + fix nullability

[stefanolsen]

Regarding the data layer. I can see that we do a join between resource and translation, when reading all resources. So the cardinality is high.
Should we split the two table queries, using multiple result sets, and then merge the data on reading?

A small optimization could be overloads to LocalizationProvider methods, without the params array parameter. In cases where those are not needed, those would take a shortcut.

[valdisiljuconoks]

I cannot rely on having MRS enabled (which is also not recommended due to potential perf. penalty).

How much gain we are talking here? I've done sandbox now with 10k resources and 5 languages. Performance is not tragic there. Sync of resources initially on startup was problem. Got it down from ~40sec to ~2sec.

[stefanolsen]

I haven't profiled the data layer, yet.

I might look into the runtime allocations first. As they can be a bigger issue on very high loads.