You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Strigun (JIRA)" <ji...@apache.org> on 2006/06/23 14:10:29 UTC
[jira] Created: (HARMONY-647) [drlvm] performance improvement for
String class
[drlvm] performance improvement for String class
------------------------------------------------
Key: HARMONY-647
URL: http://issues.apache.org/jira/browse/HARMONY-647
Project: Harmony
Type: Improvement
Components: VM
Reporter: Vladimir Strigun
Priority: Minor
I'd like to suggest performance improvement for String class. Attached patch is very simple and covers the following issues:
- Additional check in String.equals(). It returns true in case if we compare the same strings.
- Deleted temporary variable sum in String.hashCode()
- Added workaround for charset ISO-8859-1 in String.getBytes() to avoid usage of java.nio
I've execute DaCapo benchmark with the fix gives about 7% boost for Dacapo:fop bench and don't degradate on other benchmarks. Values are in milliseconds:
Build Dacapo:fop Dacapo:hsqldb Dacapo:xalan Dacapo:chart
drlvm-original 1287.076 12706.837 1933.424 16283.142
drlvm-fixed 1186.912 12471.263 1914.366 15961.693
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-647) [drlvm] performance improvement for
String class
Posted by "Geir Magnusson Jr (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-647?page=all ]
Geir Magnusson Jr updated HARMONY-647:
--------------------------------------
Component/s: DRLVM
(was: VM)
> [drlvm] performance improvement for String class
> ------------------------------------------------
>
> Key: HARMONY-647
> URL: http://issues.apache.org/jira/browse/HARMONY-647
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Reporter: Vladimir Strigun
> Priority: Minor
> Attachments: Harmony-647.patch
>
>
> I'd like to suggest performance improvement for String class. Attached patch is very simple and covers the following issues:
> - Additional check in String.equals(). It returns true in case if we compare the same strings.
> - Deleted temporary variable sum in String.hashCode()
> - Added workaround for charset ISO-8859-1 in String.getBytes() to avoid usage of java.nio
> I've execute DaCapo benchmark with the fix gives about 7% boost for Dacapo:fop bench and don't degradate on other benchmarks. Values are in milliseconds:
> Build Dacapo:fop Dacapo:hsqldb Dacapo:xalan Dacapo:chart
> drlvm-original 1287.076 12706.837 1933.424 16283.142
> drlvm-fixed 1186.912 12471.263 1914.366 15961.693
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (HARMONY-647) [drlvm] performance improvement for
String class
Posted by "Geir Magnusson Jr (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-647?page=all ]
Geir Magnusson Jr closed HARMONY-647.
-------------------------------------
Resolution: Won't Fix
We don't have String in DRLVM anymore. Please re-submit for classlib
> [drlvm] performance improvement for String class
> ------------------------------------------------
>
> Key: HARMONY-647
> URL: http://issues.apache.org/jira/browse/HARMONY-647
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Reporter: Vladimir Strigun
> Priority: Minor
> Attachments: Harmony-647.patch
>
>
> I'd like to suggest performance improvement for String class. Attached patch is very simple and covers the following issues:
> - Additional check in String.equals(). It returns true in case if we compare the same strings.
> - Deleted temporary variable sum in String.hashCode()
> - Added workaround for charset ISO-8859-1 in String.getBytes() to avoid usage of java.nio
> I've execute DaCapo benchmark with the fix gives about 7% boost for Dacapo:fop bench and don't degradate on other benchmarks. Values are in milliseconds:
> Build Dacapo:fop Dacapo:hsqldb Dacapo:xalan Dacapo:chart
> drlvm-original 1287.076 12706.837 1933.424 16283.142
> drlvm-fixed 1186.912 12471.263 1914.366 15961.693
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-647) [drlvm] performance improvement for
String class
Posted by "Vladimir Strigun (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-647?page=all ]
Vladimir Strigun updated HARMONY-647:
-------------------------------------
Attachment: Harmony-647.patch
Patch for java/lang/String class
> [drlvm] performance improvement for String class
> ------------------------------------------------
>
> Key: HARMONY-647
> URL: http://issues.apache.org/jira/browse/HARMONY-647
> Project: Harmony
> Type: Improvement
> Components: VM
> Reporter: Vladimir Strigun
> Priority: Minor
> Attachments: Harmony-647.patch
>
> I'd like to suggest performance improvement for String class. Attached patch is very simple and covers the following issues:
> - Additional check in String.equals(). It returns true in case if we compare the same strings.
> - Deleted temporary variable sum in String.hashCode()
> - Added workaround for charset ISO-8859-1 in String.getBytes() to avoid usage of java.nio
> I've execute DaCapo benchmark with the fix gives about 7% boost for Dacapo:fop bench and don't degradate on other benchmarks. Values are in milliseconds:
> Build Dacapo:fop Dacapo:hsqldb Dacapo:xalan Dacapo:chart
> drlvm-original 1287.076 12706.837 1933.424 16283.142
> drlvm-fixed 1186.912 12471.263 1914.366 15961.693
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira