[
https://issues.apache.org/jira/browse/IGNITE-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5331:
------------------------------------
Labels: performance (was: )
> Investigate performance implications of SQL schema refactoring
> --------------------------------------------------------------
>
> Key: IGNITE-5331
> URL: https://issues.apache.org/jira/browse/IGNITE-5331
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Labels: performance
> Fix For: 2.2
>
>
> SQL is now decoupled from concrete cache. It means tha:
> 1) Special cache-agnostic implementation {{CacheQueryObjectValueContext}} is
> passed to binary objects, with {{copyOnGet}} always returning true.
> 2) {{GridH2ValueCacheObject.getObject(boolean)}} is now called with {{true}}
> argument more oftner (see usages and Git history).
> All in all it means that more object copying could occur than before. We need
> to understand whether performance is affected.
> One important thing to consider is immutability of binary object. That is,
> once created, {{BinaryObject}} never changes. It means that is
> {{BinaryMarshaller}} is enabled, we can always avoid copying safely.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
