db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-1372) Handle data overrun of DDMWriter buffer more efficiently
Date Fri, 02 Jun 2006 22:18:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1372?page=all ]
Kathey Marsden resolved DERBY-1372:

    Resolution: Duplicate

Did not see that DERBY-867 was already open for this issue
Thanks Bryan for pointing this out.   I am not sure why I couldn't find it at first search.
Just  cleaning up some old todo items and trying to make sure everytthing I have is filed.

> Handle data overrun of DDMWriter buffer more efficiently
> --------------------------------------------------------
>          Key: DERBY-1372
>          URL: http://issues.apache.org/jira/browse/DERBY-1372
>      Project: Derby
>         Type: Improvement

>   Components: Network Server, Performance
>     Versions:
>     Reporter: Kathey Marsden
>     Priority: Minor

> Currently if data writing overruns DDMWriter's 32K buffer, 
> Network server will allocate a twice as big buffer and copy the 
> data.    This could be made more efficient.
> One possibility is to keep a shared pool of buffers and chain them. This might also help
with general scalability of network server.
> When this is fixed, the code in writeQRYDTA to guestimate if we 
> have enough remaining room in the block can be removed.

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