You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2006/06/02 23:55:29 UTC
[jira] Created: (DERBY-1372) Handle data overrun of DDMWriter
buffer more efficiently
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: 10.1.2.1
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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1372) Handle data overrun of DDMWriter
buffer more efficiently
Posted by "Bryan Pendleton (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1372?page=comments#action_12414527 ]
Bryan Pendleton commented on DERBY-1372:
----------------------------------------
DERBY-867 is quite closely related to this issue.
DERBY-959 and DERBY-864 also seem related, though more distantly.
> 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: 10.1.2.1
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-1372) Handle data overrun of DDMWriter buffer
more efficiently
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1372?page=all ]
Kathey Marsden closed DERBY-1372:
---------------------------------
> 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: 10.1.2.1
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1372) Handle data overrun of DDMWriter
buffer more efficiently
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ 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: 10.1.2.1
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1372) Handle data overrun of DDMWriter
buffer more efficiently
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-1372:
---------------------------------
Derby Categories: [Performance]
> Handle data overrun of DDMWriter buffer more efficiently
> --------------------------------------------------------
>
> Key: DERBY-1372
> URL: https://issues.apache.org/jira/browse/DERBY-1372
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Affects Versions: 10.1.2.1
> 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.
-
You can reply to this email to add a comment to the issue online.