[
https://issues.apache.org/jira/browse/DERBY-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633143#comment-13633143
]
Mike Matrigali commented on DERBY-6135:
---------------------------------------
good feedback, I had always assumed apps looking for compression would be
string/blob centric.
For your app do your long id's tend to start at 0 and grow? Derby internally
implements a compression technique for number data
that is highly optimized for numbers that are small but types that support much
bigger. We only use this for metadata right now.
> Request data compression scheme (i.e., gzip of data pages)
> ----------------------------------------------------------
>
> Key: DERBY-6135
> URL: https://issues.apache.org/jira/browse/DERBY-6135
> Project: Derby
> Issue Type: Improvement
> Components: Store
> Reporter: Tony Brusseau
>
> This is a request for a data compression scheme facility added to Derby
> (something like gzip of data pages). MySQL and some other databases provide
> such a feature, see:
> http://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-compression-internals.html
> The desire for this is because my current database size is 27GB but gzipped,
> it goes down to 7GB. I wish to scale my database dramatically, but the
> current disk footprint would prevent me from being able to use Derby.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
