ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Scherbakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8873) Optimize cache scans with enabled persistence.
Date Tue, 25 Jun 2019 20:21:01 GMT

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

Alexei Scherbakov commented on IGNITE-8873:
-------------------------------------------

[~dmagda]

This method was added to address exactly the case where huge (tens of terabytes) cache have
to be efficiently fully scanned.
It was already successfully used in production by some Ignite users as far as I know.
The main idea behind per partition preloading API same as for other methods working with partitions:
affinity run/call, scan by partition, SQL query by partition(s).
I suggest to keep this method for advanced use cases and add some more "high level" APIs like
you have proposed.

> 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)

Mime
View raw message