[
https://issues.apache.org/jira/browse/IGNITE-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663918#comment-16663918
]
Alexei Scherbakov commented on IGNITE-8873:
-------------------------------------------
[~agoncharuk],
1) The main use case for this method is preloading for iteration using scan or
sql query over partition which is almost always done over primary partition.
Backup partitions are not intended for use from public API, so I do not think
it's necessary to preload backups.
I've added {{preloadPartitionLocal}} method as you suggested which could be
used for preloading of any local partition. By combining compute API and this
method backup partition can be preloaded if needed.
2) Done
3) Done. Added two new tests {{testPreloadPartitionInMemoryRemote,
testPreloadPartitionInMemoryLocal}}
Please review.
> 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)
