db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-684) Improve performance of Clob objects (ClobOutputStream#write,ClobWriter#write) on the client
Date Sat, 05 Nov 2005 02:10:19 GMT
Improve performance of Clob objects (ClobOutputStream#write,ClobWriter#write) on the client


         Key: DERBY-684
         URL: http://issues.apache.org/jira/browse/DERBY-684
     Project: Derby
        Type: Improvement
  Components: Performance, Network Client  
 Environment: all
    Reporter: Sunitha Kambhampati

Dan suggested this improvement  here:

For org.apache.derby.client.am.ClobOutputStream#write(int), five objects are created for every
byte written.

"In fact this class and the client Clob have code like this everywhere, as the Clob is updated:

        clob_.string_ = clob_.string_.concat(new String(newByte));
        clob_.asciiStream_ = new java.io.StringBufferInputStream(clob_.string_);
        clob_.unicodeStream_ = new java.io.StringBufferInputStream(clob_.string_);
        clob_.characterStream_ = new java.io.StringReader(clob_.string_);

Would probably be better to create most of those objects on demand, rather than on every modification.
I mean if the CLOB is modified
but the application never retrieives the ascii  or character streams, what was the benefit
of creating them? "
Also check the org.apache.derby.client.am.ClobWriter.  Need to make this better and efficient.

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