ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladislav Pyatkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8873) Optimize cache scans with enabled persistence.
Date Tue, 10 Jul 2018 10:49:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538387#comment-16538387

Vladislav Pyatkov commented on IGNITE-8873:

I think, that will to by done across preload every partition pages before iterate over entry.

And other idea: to implement specific configuration parameter (like \{{CacheConfiguration#warnUpOnStart(boolean)}}),
that preload all pages from storage for particular cache (cache group) after the cache started.

Anyone have idea, how to implement it in public API?

> 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
>            Priority: Major
>             Fix For: 2.7
> 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

View raw message