You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/05/29 14:02:04 UTC
[jira] [Created] (IGNITE-5331) Investigate performance implications
of SQL schema refactoring
Vladimir Ozerov created IGNITE-5331:
---------------------------------------
Summary: 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
Fix For: 2.1
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)