harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Strigun (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-630) Performance improvement for BufferedReader and LineNumberReader classes
Date Tue, 20 Jun 2006 19:23:30 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-630?page=all ]

Vladimir Strigun updated HARMONY-630:

    Attachment: Harmony-630.patch

Please try my patch

> Performance improvement for BufferedReader and LineNumberReader classes
> -----------------------------------------------------------------------
>          Key: HARMONY-630
>          URL: http://issues.apache.org/jira/browse/HARMONY-630
>      Project: Harmony
>         Type: Improvement

>   Components: Classlib
>     Reporter: Vladimir Strigun
>     Priority: Minor
>  Attachments: Harmony-630.patch
> Analysis of BufferedReader and LineNumberReader was made by our team. These classes are
widely used and it's recommended, for instance, that any character IO should go through BufferedReader
for better performance. Therefore it should perform well and should not itself be a bottleneck.

> We have identified opportunity to increase performance of mentioned classes. Publicly
available bench DaCapo[1] was used for performance measurement and we found that DaCapo:hsqldb
benchmark performance can be improved within small modification of java.io.BufferedReader
and java.io.LineNumberReader classes. Main idea of the patch (I will attach it soon) is to
remove StringBuilder allocation from "malloc"-hot methods readLine. 
> Here is result of DaCapo execution with patched and original versions of classlib+J9:
> Build	Dacapo: fop	Dacapo: hsqldb	Dacapo: xalan	Dacapo: chart	
> original	712.020	27232.647	4201.449	22573.192	
> patched	715.152	26703.966	4161.018	22580.771	
> [1] http://www-ali.cs.umass.edu/DaCapo/gcbm.html

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message