<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 73: bloat in xalan harness</title><link href="https://sourceforge.net/p/dacapobench/bugs/73/" rel="alternate"/><link href="https://sourceforge.net/p/dacapobench/bugs/73/feed.atom" rel="self"/><id>https://sourceforge.net/p/dacapobench/bugs/73/</id><updated>2010-03-24T03:44:49Z</updated><subtitle>Recent changes to 73: bloat in xalan harness</subtitle><entry><title>bloat in xalan harness</title><link href="https://sourceforge.net/p/dacapobench/bugs/73/" rel="alternate"/><published>2010-03-24T03:44:49Z</published><updated>2010-03-24T03:44:49Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netcb36f90e45b5ea1be69ec81a661a22fbf4aa78ea</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I was doing research on program analysis techniques targeting runtime bloat.  I have recently developed a static analysis  to find objects and calls that can be pulled out of loops.  One interesting warning that the tool reported for DaCapo/xalan was in method "run" of class "dacapo.xalan.XalanHarness" (in the 2006 version).  At line 88 of the class, a new transformer is created by calling "_template.newTransformer()".  My tool suggested to pull this call out of the while loop starting at line 83.  I inspected the source code and found this was actually true, because we don't need to create a transformer per input file. When I get this call pulled out, I could see 10% running time reduction and the number of objects created was reduced by almost a million (on IBM J9 1.5.0 build 2.4).   I also checked the latest version of DaCapo, and found it was still inside the loop (line 86 of class  org.dacapo.xalan.XSLTBench).&lt;/p&gt;
&lt;p&gt;I am wondering if this is indeed a performance problem, or a false warning reported by our tool.  Thank you ! &lt;/p&gt;&lt;/div&gt;</summary></entry></feed>