You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by theseusyang <th...@gmail.com> on 2016/06/09 01:50:55 UTC
add 'ZeroCopy' functions into geode
Hi All,
Because when Geode continue writing Entry into cache , then frequently
switching Cache Context to Disk File Context, it seriously affect
performance , cause high-latency response.
Maybe 'Zero Copy' is a referenced solutions, Any body is interested in this
feature?
theseus yang
--
View this message in context: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/add-ZeroCopy-functions-into-geode-tp6513.html
Sent from the Apache Geode (Incubating) Developers Forum mailing list archive at Nabble.com.
Re: add 'ZeroCopy' functions into geode
Posted by Anilkumar Gingade <ag...@pivotal.io>.
As i know we try to avoid copying as much as possible....When we read from
socket to storing in cache...Its mostly the reference pointer that is
passed around...Someone can correct me if i am wrong....
I am interested to see how adopting techniques to reduce cache-miss rates
(L1/L2) will help Geode...
-Anil.
On Thu, Jun 9, 2016 at 12:51 PM, Swapnil Bawaskar <sb...@pivotal.io>
wrote:
> In Geode latest data is in memory and the least recently used data can be
> overflowed to disk. Since data coming in from the sockets is the latest
> data which needs to kept in memory, I don't think zero copy will be
> helpful. On the other hand, when there is a read request for data already
> overflown to disk, we could use zero copy to write directly from disk to
> the socket.
>
> I think we could make storing data in "off-heap" work while inserting data;
> provided there are no callbacks to be invoked.
>
> On Wed, Jun 8, 2016 at 6:50 PM, theseusyang <th...@gmail.com> wrote:
>
> > Hi All,
> >
> > Because when Geode continue writing Entry into cache , then frequently
> > switching Cache Context to Disk File Context, it seriously affect
> > performance , cause high-latency response.
> >
> > Maybe 'Zero Copy' is a referenced solutions, Any body is interested in
> this
> > feature?
> >
> >
> > theseus yang
> >
> >
> >
> > --
> > View this message in context:
> >
> http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/add-ZeroCopy-functions-into-geode-tp6513.html
> > Sent from the Apache Geode (Incubating) Developers Forum mailing list
> > archive at Nabble.com.
> >
>
Re: add 'ZeroCopy' functions into geode
Posted by Swapnil Bawaskar <sb...@pivotal.io>.
In Geode latest data is in memory and the least recently used data can be
overflowed to disk. Since data coming in from the sockets is the latest
data which needs to kept in memory, I don't think zero copy will be
helpful. On the other hand, when there is a read request for data already
overflown to disk, we could use zero copy to write directly from disk to
the socket.
I think we could make storing data in "off-heap" work while inserting data;
provided there are no callbacks to be invoked.
On Wed, Jun 8, 2016 at 6:50 PM, theseusyang <th...@gmail.com> wrote:
> Hi All,
>
> Because when Geode continue writing Entry into cache , then frequently
> switching Cache Context to Disk File Context, it seriously affect
> performance , cause high-latency response.
>
> Maybe 'Zero Copy' is a referenced solutions, Any body is interested in this
> feature?
>
>
> theseus yang
>
>
>
> --
> View this message in context:
> http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/add-ZeroCopy-functions-into-geode-tp6513.html
> Sent from the Apache Geode (Incubating) Developers Forum mailing list
> archive at Nabble.com.
>