ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandr Fedotov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-5721) Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge allocation of org.apache.ignite.internal.binary.BinaryReaderExImpl instances
Date Mon, 10 Jul 2017 11:17:00 GMT

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

Alexandr Fedotov updated IGNITE-5721:
-------------------------------------
    Description: 
Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge allocation of
 org.apache.ignite.internal.binary.BinaryReaderExImpl instances in org.apache.ignite.internal.binary.BinaryUtils#doReadObject
method.
Optimizing this point should reduce memory pressure.

An example of memory allocation in a read only scenario



  was:
Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge allocation of
 org.apache.ignite.internal.binary.BinaryReaderExImpl instances in org.apache.ignite.internal.binary.BinaryUtils#doReadObject
method.
Optimizing this point should reduce memory pressure.




> Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge allocation
of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-5721
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5721
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.0
>            Reporter: Alexandr Fedotov
>              Labels: 2.0
>             Fix For: 2.2
>
>
> Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge allocation
of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances in org.apache.ignite.internal.binary.BinaryUtils#doReadObject
method.
> Optimizing this point should reduce memory pressure.
> An example of memory allocation in a read only scenario



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message