db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1679) Improve usage of file resources when sorting
Date Thu, 21 Jun 2007 23:23:25 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507067

Bryan Pendleton commented on DERBY-1679:

Mike and I had a related discussion on the developer's list. I asked whether there were ways
to control Derby's use of open file descriptors, since that has been causing me some troubles
with resource management in an application server environment. 

Mike's thoughts on file descriptor usage and on resource controls are here:

> Improve usage of file resources when sorting
> --------------------------------------------
>                 Key: DERBY-1679
>                 URL: https://issues.apache.org/jira/browse/DERBY-1679
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions:,,,,,
>            Reporter: Sunitha Kambhampati
>            Priority: Minor
> Currently each sort merge run is put into a separate file.  Worst case,  the sot module
can use 512 open files per connection. 
> This jira is to investigate how to improve file resources usage. Derby server should
maintain some control on open files.
> Mike suggested that one solution could be to tie the open files into something like the
open file cache in the store, or maybe just store all the sort runs in a single file - i think
they are written sequentially so may not be hard to do using existing streamed file support
in the store.
> Also see derby-1661.

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

View raw message