Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 06E64200C7F for ; Wed, 24 May 2017 09:19:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 05ED6160B9C; Wed, 24 May 2017 07:19:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 30D38160BD7 for ; Wed, 24 May 2017 09:19:08 +0200 (CEST) Received: (qmail 98318 invoked by uid 500); 24 May 2017 07:19:07 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 98282 invoked by uid 99); 24 May 2017 07:19:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 May 2017 07:19:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 01A5A1A0068 for ; Wed, 24 May 2017 07:19:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id HjoDy8c-lKJB for ; Wed, 24 May 2017 07:19:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id DE05A5FDD2 for ; Wed, 24 May 2017 07:19:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 66BDFE0D9D for ; Wed, 24 May 2017 07:19:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 777C521B5F for ; Wed, 24 May 2017 07:19:04 +0000 (UTC) Date: Wed, 24 May 2017 07:19:04 +0000 (UTC) From: "Yakov Zhdanov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-4683) Need to avoid extra-copy to byte array when marshalling to cache object (e.g. return ByteBuffer) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 24 May 2017 07:19:09 -0000 [ https://issues.apache.org/jira/browse/IGNITE-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Zhdanov updated IGNITE-4683: ---------------------------------- Description: Now, when Ignite marshals to cache object it marshals to byte array and then strips the byte array to return array of exact size. In most cases marshalled objects are sent via network or copied to offheap, so last step with copying data to a new array is not needed. # We can add overload for marshalling methods to return ByteBuffer. # Probably, we will need some new CacheObject implementations to wrap ByteBuffer. # We will need to add support for ByteBuffers to direct marshaller > Need to avoid extra-copy to byte array when marshalling to cache object (e.g. return ByteBuffer) > ------------------------------------------------------------------------------------------------ > > Key: IGNITE-4683 > URL: https://issues.apache.org/jira/browse/IGNITE-4683 > Project: Ignite > Issue Type: Improvement > Components: cache > Reporter: Yakov Zhdanov > Assignee: Igor Seliverstov > Fix For: 2.1 > > > Now, when Ignite marshals to cache object it marshals to byte array and then strips the byte array to return array of exact size. In most cases marshalled objects are sent via network or copied to offheap, so last step with copying data to a new array is not needed. > # We can add overload for marshalling methods to return ByteBuffer. > # Probably, we will need some new CacheObject implementations to wrap ByteBuffer. > # We will need to add support for ByteBuffers to direct marshaller -- This message was sent by Atlassian JIRA (v6.3.15#6346)