You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2001/08/10 18:41:39 UTC

[Bug 3085] New: - StringPool and SymbolCahce performance problems

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3085

*** shadow/3085	Fri Aug 10 09:41:39 2001
--- shadow/3085.tmp.15115	Fri Aug 10 09:41:39 2001
***************
*** 0 ****
--- 1,26 ----
+ +============================================================================+
+ | StringPool and SymbolCahce performance problems                            |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 3085                        Product: Xerces-J                |
+ |       Status: NEW                         Version: 1.4.2                   |
+ |   Resolution:                            Platform: All                     |
+ |     Severity: Normal                   OS/Version: All                     |
+ |     Priority: Other                     Component: Core                    |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: xerces-j-dev@xml.apache.org                                  |
+ |  Reported By: sszego@saba.com                                              |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ In both StringPool and SymbolCache the following code pattern is used:
+ try {
+    array[index] = x;
+ }
+ catch (ArrayIndexOutOfBoundsException ex) {
+    array = makeArrayBigger(array);
+ ...
+ }
+ As it turns out throwing and catching an exception is costlier in more taxing 
+ in a multi-user environment than comparing the index value to the array size.
\ No newline at end of file

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org