You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2012/10/05 16:50:02 UTC
[jira] [Commented] (ACCUMULO-786) Look into walog space usage
[ https://issues.apache.org/jira/browse/ACCUMULO-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470363#comment-13470363 ]
Eric Newton commented on ACCUMULO-786:
--------------------------------------
The mutation serialization code is pretty simple: lengths are encoded as 4-byte signed integers, timestamps which are normally not set by the user, are encoded as 8-byte signed longs. There's roughly 36 bytes of overhead for an empty mutation.
We could encode the lengths and timestamps as variable-length integers. It might not be worth the extra encoding/decoding time, though. We'll need to experiment.
> Look into walog space usage
> ---------------------------
>
> Key: ACCUMULO-786
> URL: https://issues.apache.org/jira/browse/ACCUMULO-786
> Project: Accumulo
> Issue Type: Task
> Reporter: Keith Turner
> Fix For: 1.5.0
>
>
> I was experimenting with write ahead log write performance and noticed that when I wrote 1G of data that the walog was 1.5G.
--
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