db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1677) Investigate increasing the memory limit that is used to calculate the sortbuffer size for sorting.
Date Mon, 29 Jun 2009 14:33:47 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dag H. Wanvik updated DERBY-1677:
---------------------------------

    Derby Categories: [Performance]

> Investigate increasing the memory limit that is used to calculate the sortbuffer size
for sorting.
> --------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1677
>                 URL: https://issues.apache.org/jira/browse/DERBY-1677
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6
>            Reporter: Sunitha Kambhampati
>
> The sortbuffer is the in memory sort buffer and the size of the sort buffer is calculated
using the default memory limit  of 1M if derby.storage.sortBufferMax is not specified. . 
> This may not be appropriate for large systems. Investigate if we can up this value. 
> see org.apache.derby.impl.store.access.sort.ExternalSortFactory
> protected static final int DEFAULT_MEM_USE = 1024*1024; // aim for about 1Meg
> The calculations to come up with the initial size for sortbuffer is in ExternalSortFactory.createSort()
> 	

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message