ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-3245) IGFS: Optimize performance for client nodes.
Date Thu, 30 Jun 2016 11:24:10 GMT

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

Vladimir Ozerov resolved IGNITE-3245.
-------------------------------------
    Resolution: Fixed

> IGFS: Optimize performance for client nodes.
> --------------------------------------------
>
>                 Key: IGNITE-3245
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3245
>             Project: Ignite
>          Issue Type: Task
>          Components: IGFS
>    Affects Versions: 1.6
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>             Fix For: 1.7
>
>
> *Problem*
> Ignite can work in two modes - server (default) and client. Both modes provide transparent
cache API. 
> IGFS heavily rely on cache operations and sometimes perform lots of them with assumption
that metadata is located on the same node, so these operations are cheap and do not require
any cross-node communication. 
> But when user works with IGFS from client node, this code could be very inefficient because
even single operation could cause many network round trips between a client and a server.
> *Solution*
> Provide special implementations of IGFS operations which will delegate the whole execution
to the server, thus leaving only a single network round trip.



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

Mime
View raw message