You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@usergrid.apache.org by "Todd Nine (JIRA)" <ji...@apache.org> on 2015/01/26 18:19:35 UTC

[jira] [Updated] (USERGRID-365) Optimize Entity Storage

     [ https://issues.apache.org/jira/browse/USERGRID-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Nine updated USERGRID-365:
-------------------------------
    Description: 
Currently our entity storage is very bloated.  I propose the following changes to increase our network performance to Cassandra.

# Stop storing FQDN of classes, instead use a lookup table in the application itself
# Remove the index flags on the properties.  Everything is indexed, and this causes unnecessary data bloat
# Possibly investigate compression client side, though this should be a last resort



> Optimize Entity Storage
> -----------------------
>
>                 Key: USERGRID-365
>                 URL: https://issues.apache.org/jira/browse/USERGRID-365
>             Project: Usergrid
>          Issue Type: Story
>            Reporter: Todd Nine
>             Fix For: 2.0
>
>
> Currently our entity storage is very bloated.  I propose the following changes to increase our network performance to Cassandra.
> # Stop storing FQDN of classes, instead use a lookup table in the application itself
> # Remove the index flags on the properties.  Everything is indexed, and this causes unnecessary data bloat
> # Possibly investigate compression client side, though this should be a last resort



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)