Hi All, I'm working with embedded Derby (10.5.1.1).
The regular embedded mode (file system based) works fine and no problems at all but if the database is zipped / jarred and accessed via a jar file (read-only), the selects take a lot of time. Is this a known issue? I have set the following properties: derby.storage.pageSize derby.storage.pageCacheSize derby.storage.tempDirectory derby.stream.error.file Thanks for your time and effort. -- View this message in context: http://www.nabble.com/Performance-issues-with-zipped-up-derby-database-tp24894232p24894232.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
