Hello, > > Also, to apply this kind of patch that will affect everything, I would > > like to know in advance the memory footprint (running mono --profile > > before/after should tell us this) and how much extra code is JITed at > > startup (how much slower this becomes for a sample program). > > I agree with Ben that string are localized only several time and the little > performance overhead caused by localization can be ignored. (The overhead > should be little.)
Yes, but Ben limited himself to speculation. I want to know the real impact (we have the tools, it should take a few minutes at most to find out the numbers). > And as I told several times in this topic the current ResourceSet is not > efficient. ResourceManager of MS.NET uses a custom resource set called > RuntimeResourceSet (private type, ResourceSet of MS.NET does the same as > Mono's one) that loads each resource (either string or object) when it is > needed instead of loading all of them at construction. It caches resource > once they was loaded. This could be used in Mono as well or if we want we > could use a ResourceSet that does no caching at all. But the advantages and > disadvantages of using no cache should be compared in real life before > making a decission. Ah, interesting. Am not familiar with this, but it sounds like we should look into implementing this functionality. > It's good.:) By the way, the most important thing: key/string technique will > have the same performance and memory requirements if you use the same > ResourceManager and ResourceSet classes. The only difference will be that it > will look up even English resources in a file that means some performance > overhead but I think it's so little that it can be ignored. Well, I still want to have numbers at hand so we can make a decision. Miguel. _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list