db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Brusseau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6135) Request data compression scheme (i.e., gzip of data pages)
Date Tue, 16 Apr 2013 17:39:17 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633051#comment-13633051

Tony Brusseau commented on DERBY-6135:

The size I gave was after running SYSCS_UTIL.SYSCS_COMPRESS_TABLE on all the tables.

du -sh log 
1.1M	log

du -sh seg0
29G seg0

All the data is in seg0.

I don't think the datatype level would help since only a very tiny bit of the data in my particular
case is in strings, clobs and lobs.

I use long ids everywhere, I bet a bunch of the gzip compression is from compression of replicated
bytes in the ids.

> 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

View raw message