You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Valentin Kulichenko (JIRA)" <ji...@apache.org> on 2017/01/25 00:39:26 UTC
[jira] [Issue Comment Deleted] (IGNITE-2488) Investigate possible
Hibernate Ignite L2 Cache performance issues
[ https://issues.apache.org/jira/browse/IGNITE-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Kulichenko updated IGNITE-2488:
----------------------------------------
Comment: was deleted
(was: Thank you for your email, I will be out of the office on extended leave from November 14, 2016, to March 6, 2017. I will have no access to email during this time. If you require further assistance, please contact Yulia Lukash, [1]yulia@gridgain.com or call at (650) 241-2281.
Thank you for your understanding.
Best regards,
--
Dinara DubeOperations Manager650-224-4919
----------------------------------------------------------------------------------------
[1] mailto:yulia@gridgain.com
)
> Investigate possible Hibernate Ignite L2 Cache performance issues
> -----------------------------------------------------------------
>
> Key: IGNITE-2488
> URL: https://issues.apache.org/jira/browse/IGNITE-2488
> Project: Ignite
> Issue Type: Bug
> Components: cache, Hibernate L2 cache
> Affects Versions: 1.5.0.final
> Reporter: Denis Magda
> Assignee: Vladimir Ershov
> Labels: community
>
> The ticket is opened as a part of the discussion happened on StackOverflow [1].
> There is a suspicion that Ignite L2 cache has some performance bottlenecks.
> Need to reproduce and investigate.
> [1] http://stackoverflow.com/questions/34534251/ignite-for-hibernate-l2-is-extremely-slow/34551411#34551411
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)