<!-- 
RSS generated by JIRA (4.4#649-r158309) at Wed Jun 19 10:26:00 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://dev.clojure.org/jira/si/jira.issueviews:issue-xml/CLJ-1005/CLJ-1005.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Clojure JIRA</title>
    <link>http://dev.clojure.org/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>4.4</version>
        <build-number>649</build-number>
        <build-date>25-07-2011</build-date>
    </build-info>

<item>
            <title>[CLJ-1005] Use transient map in zipmap</title>
                <link>http://dev.clojure.org/jira/browse/CLJ-1005</link>
                <project id="10010" key="CLJ">Clojure</project>
                        <description>&lt;p&gt;The attached patch changes zipmap to use a transient map internally. The definition is also moved so that it resides below that of #&apos;transient. The original definition is commented out (like that of #&apos;into).&lt;/p&gt;</description>
                <environment></environment>
            <key id="15491">CLJ-1005</key>
            <summary>Use transient map in zipmap</summary>
                <type id="4" iconUrl="http://dev.clojure.org/jira/images/icons/improvement.gif">Enhancement</type>
                                <priority id="3" iconUrl="http://dev.clojure.org/jira/images/icons/priority_major.gif">Major</priority>
                    <status id="1" iconUrl="http://dev.clojure.org/jira/images/icons/status_open.gif">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="aaron">Aaron Bedra</assignee>
                                <reporter username="michalmarczyk">Micha&#322; Marczyk</reporter>
                        <labels>
                    </labels>
                <created>Wed, 30 May 2012 02:55:43 -0500</created>
                <updated>Thu, 11 Apr 2013 18:19:28 -0500</updated>
                                    <version>Release 1.6</version>
                                <fixVersion>Release 1.6</fixVersion>
                                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="29156" author="aaron" created="Tue, 14 Aug 2012 21:24:43 -0500"  >&lt;p&gt;Why is the old implementation left and commented out? If we are going to move to a new implementation, the old one should be removed.&lt;/p&gt;</comment>
                    <comment id="29164" author="michalmarczyk" created="Wed, 15 Aug 2012 04:17:00 -0500"  >&lt;p&gt;As mentioned in the ticket description, the previously attached patch follows the pattern of into whose non-transient-enabled definition is left in core.clj with a #_ in front &amp;#8211; I wasn&apos;t sure if that&apos;s something desirable in all cases.&lt;/p&gt;

&lt;p&gt;Here&apos;s a new patch with the old impl removed.&lt;/p&gt;</comment>
                    <comment id="29170" author="jafingerhut" created="Wed, 15 Aug 2012 10:37:04 -0500"  >&lt;p&gt;Thanks for the updated patch, Michal.  Sorry to raise such a minor issue, but would you mind using a different name for the updated patch?  I know JIRA can handle multiple attached files with the same name, but my prescreening code isn&apos;t quite that talented yet, and it can lead to confusion when discussing patches.&lt;/p&gt;</comment>
                    <comment id="29171" author="michalmarczyk" created="Wed, 15 Aug 2012 10:42:40 -0500"  >&lt;p&gt;Thanks for the heads-up, Andy! I&apos;ve reattached the new patch under a new name.&lt;/p&gt;</comment>
                    <comment id="29197" author="jafingerhut" created="Thu, 16 Aug 2012 20:24:44 -0500"  >&lt;p&gt;Presumptuously changing Approval from Incomplete back to None after the Michal&apos;s updated patch was added, addressing the reason the ticket was marked incomplete.&lt;/p&gt;</comment>
                    <comment id="30930" author="aaron" created="Thu, 11 Apr 2013 17:32:24 -0500"  >&lt;p&gt;The patch looks good and applies cleanly. Are there additional tests that we should run to verify that this is providing the improvement we think it is. Also, is there a discussion somewhere that started this ticket? There isn&apos;t a lot of context here.&lt;/p&gt;</comment>
                    <comment id="30932" author="michalmarczyk" created="Thu, 11 Apr 2013 18:19:28 -0500"  >&lt;p&gt;Hi Aaron,&lt;/p&gt;

&lt;p&gt;Thanks for looking into this!&lt;/p&gt;

&lt;p&gt;From what I&apos;ve been able to observe, this change hugely improves &lt;tt&gt;zipmap&lt;/tt&gt; times for large maps. For small maps, there is a small improvement. Here are two basic Criterium benchmarks (&lt;tt&gt;transient-zipmap&lt;/tt&gt; defined at the REPL as in the patch):&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;;;; large map
user=&amp;gt; (def xs (range 16384))
#&apos;user/xs
user=&amp;gt; (last xs)
16383
user=&amp;gt; (c/bench (zipmap xs xs))
Evaluation count : 13920 in 60 samples of 232 calls.
             Execution time mean : 4.329635 ms
    Execution time std-deviation : 77.791989 us
   Execution time lower quantile : 4.215050 ms ( 2.5%)
   Execution time upper quantile : 4.494120 ms (97.5%)
nil
user=&amp;gt; (c/bench (transient-zipmap xs xs))
Evaluation count : 21180 in 60 samples of 353 calls.
             Execution time mean : 2.818339 ms
    Execution time std-deviation : 110.751493 us
   Execution time lower quantile : 2.618971 ms ( 2.5%)
   Execution time upper quantile : 3.025812 ms (97.5%)

Found 2 outliers in 60 samples (3.3333 %)
	low-severe	 2 (3.3333 %)
 Variance from outliers : 25.4675 % Variance is moderately inflated by outliers
nil

;;; small map
user=&amp;gt; (def ys (range 16))
#&apos;user/ys
user=&amp;gt; (last ys)
15
user=&amp;gt; (c/bench (zipmap ys ys))
Evaluation count : 16639020 in 60 samples of 277317 calls.
             Execution time mean : 3.803683 us
    Execution time std-deviation : 88.431220 ns
   Execution time lower quantile : 3.638146 us ( 2.5%)
   Execution time upper quantile : 3.935160 us (97.5%)
nil
user=&amp;gt; (c/bench (transient-zipmap ys ys))
Evaluation count : 18536880 in 60 samples of 308948 calls.
             Execution time mean : 3.412992 us
    Execution time std-deviation : 81.338284 ns
   Execution time lower quantile : 3.303888 us ( 2.5%)
   Execution time upper quantile : 3.545549 us (97.5%)
nil
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Clearly the semantics are preserved provided transients satisfy their contract.&lt;/p&gt;

&lt;p&gt;I think I might not have started a ggroup thread for this, sorry.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                    <attachment id="11432" name="0001-Use-transient-map-in-zipmap.2.patch" size="1722" author="michalmarczyk" created="Wed, 15 Aug 2012 10:40:53 -0500" />
                    <attachment id="11269" name="0001-Use-transient-map-in-zipmap.patch" size="1281" author="michalmarczyk" created="Wed, 30 May 2012 02:55:43 -0500" />
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Global Rank</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                            <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                <customfieldname>Patch</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10001">Code</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                        </customfields>
    </item>
</channel>
</rss>