Interesting.<\/p>\n
A review from 2007 contains this:<\/p>\n
\n{smartassembly} uses several different techniques to bring down the memory usage.<\/p>\n
We asked the developers of {smartassembly} for some of the specifics, and they told us that by default the CLR reserves a ton of memory for .NET assemblies – whether or not they request it. So {smartassembly} intelligently detects when the CPU is idle (or thereabout) and increases or decreases the amount of reserved memory for your assembly according to its requirements – “automated” GC in a sense, except that memory may or may not have ever been in use.<\/p>\n
In that same vein, {smartassembly} (with the benefit of literally having access to your source code thanks to the way .NET is designed) marks any and all classes that don’t have any detectable “child” classes inheriting from them as “sealed” thereby reducing the amount of memory and CPU used by the CLR during run-time to determine what functions should be made available to other classes and libraries.<\/p>\n<\/blockquote>\n
The same review has a “before\/after” pair of screenshots showing an application going from 8M to 420K. This suggests to me that it’s actually just reducing the working set of the application, not the real memory requirements. The same “optimisation” appears to occur if you minimise an app. It doesn’t suddenly take up less memory. I don’t believe the desktop .NET framework can really<\/em> run with only 420K.<\/p>\n
The automatic sealing feature is interesting – I can’t see that it helps other than for lookup of virtual methods. I doubt that the impact is really significant, but of course I haven’t benchmarked it.<\/p>\n
So, nothing conclusive, but I doubt that it’s doing anything that I’d particularly want.<\/p>\n","protected":false},"excerpt":{"rendered":"
Interesting. A review from 2007 contains this: {smartassembly} uses several different techniques to bring down the memory usage. We asked the developers of {smartassembly} for some of the specifics, and they told us that by default the CLR reserves a ton of memory for .NET assemblies – whether or not they request it. So {smartassembly} […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-4915","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/4915","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/comments?post=4915"}],"version-history":[{"count":0,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/4915\/revisions"}],"wp:attachment":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/media?parent=4915"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/categories?post=4915"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/tags?post=4915"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}