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/06/05 14:27:59 UTC
[jira] [Created] (IGNITE-3245) IGFS: Optimize performance for
client nodes.
Vladimir Ozerov created IGNITE-3245:
---------------------------------------
Summary: 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)