[IGNITE-7638] Page replacement process in PDS mode affect segment loaded pages table performance

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.5
• Component/s: persistence
• Assignee: Dmitry Pavlov
• Reporter: Dmitry Pavlov
• Created: 06/Feb/18 17:44
• Updated: 21/Mar/18 09:24
• Resolved: 13/Mar/18 13:38

Description

There is

• durable memory segment in PDS enabled data region
• page replacement started

then Ignite performance slow down occurs, JFR & Visual VM shows get&put from FullPageIdTable requires significiant time to be executed (~5-10% оf samples count and up to 40% CPU usage)

Avg steps in loaded pages table, get: 9456 steps,  put: 20243 steps,  capacity: 20242 size: 7978

Effect of influence of FullPageID table is cumulative, once it starts to grow, number of steps required grows also.

Issue Links

• causes: IGNITE-7965 Robin-hood hashing may fail with negative index in case backward shift finished with full table scan
• relates to: IGNITE-7698 Page read during replacement should be outside of segment write lock
• links to: GitHub Pull Request #3481