I have a large cloudscape 5 database (over 5million records) and I have found that when a ResultsSet includes all or many of these records, the initial call to ResultsSet.next() takes a very long (but finite) time (I would estimate about 10-15mins) . I can (indeed have) arrange the code so that this call occurs in a separate java thread which can be interrupted from the UI thread. BUT, as you may know, java threads that are set to as interrupted continue to execute until either application code or some "system" calls actually check the interrupted state of the running thread.
So, given this background info, my questions on Derby are 1. Have any significant performance improvements been made such that, for databases of this size, migrating from cloudscape to Derby would provide a significantly better response time ? 2. If not, are there any improvements to the responsiveness of the timeconsuming call to .next() to the setting of the interrupted flag on the current thread in Derby ? Thanks Phil Cope -- View this message in context: http://www.nabble.com/Thread-Interruption-in-large-Database-tp17865036p17865036.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
