On Mon, Jan 4, 2010 at 7:13 AM, Attila Szegedi <[email protected]> wrote:
> In my other project, FreeMarker, I implemented optional caching of > wrappers. By default, it is turned off. I heard of some people that > turned it on, but in most use cases, there are no noticeable > performance differences. > > While you should test every performance hypothesis with a profiler, > the common presumption these days is that these objects are > sufficiently light to create that their repeated creation and > collection (they'll likely not even survive the first eden space > collection) is too insignificant burden to the GC to justify keeping > them around. > > They're simply too light to cache. > > My concern was not memory use but the expense of method lookups via reflection. I imagine Rhino does a lot of caching of the lookups, then? -- Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com mailto:[email protected] _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
