You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/03/18 19:14:33 UTC

[jira] [Closed] (IGNITE-2813) IGFS: Optimize IgfsFileInfo format.

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

Vladimir Ozerov closed IGNITE-2813.
-----------------------------------

> IGFS: Optimize IgfsFileInfo format.
> -----------------------------------
>
>                 Key: IGNITE-2813
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2813
>             Project: Ignite
>          Issue Type: Task
>          Components: IGFS
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>             Fix For: 1.7
>
>
> *Problem*
> Currently our metadata appears to be too heavy. 
> Short summary of {{IgfsFIleInfo}}:
> {{id}} - files and dirs 
> {{len}} - only files
> {{blockSize}} - only files
> {{props}} - files and dirs
> {{lockId}} - only files
> {{affKey}} - only files
> {{fileMap}} - only files
> {{accessTime}} - files and dirs
> {{modificationTime}} - files and dirs
> {{listing}} - only dirs
> {{evictExclude}} - only files
> The same applies to {{IgfsListingEntry}}
> *Solution*
> 1) Split files and directories into separate classes. This will improve both performance and maintainability of {{IgfsFileInfo}} class.
> 2) Investigate whether we need {{IgfsListingEntry}} at all. It looks like we only need it for "listPaths" operation. Can we simply replace it with "String -> IgniteUuid" map?



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