You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/22 19:46:00 UTC
[jira] [Commented] (IGNITE-8873) Optimize cache scans with enabled
persistence.
[ https://issues.apache.org/jira/browse/IGNITE-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659584#comment-16659584 ]
ASF GitHub Bot commented on IGNITE-8873:
----------------------------------------
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/5053
IGNITE-8873 Preload cache partition into page memory.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8873
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5053.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5053
----
----
> Optimize cache scans with enabled persistence.
> ----------------------------------------------
>
> Key: IGNITE-8873
> URL: https://issues.apache.org/jira/browse/IGNITE-8873
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexei Scherbakov
> Assignee: Alexei Scherbakov
> Priority: Major
> Fix For: 2.8
>
>
> Currently cache scans with enabled persistence involve link resolution, which can lead to radom disk access resulting in bad performace on SAS disks.
> One possibility is to preload cache data pages to remove slow random disk access.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)