[
https://issues.apache.org/jira/browse/IGNITE-27688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Pligin updated IGNITE-27688:
-------------------------------------
Description:
h3. Background
In Apache Ignite 2, the {{getPagesFillFactor()}} method in
{{DataRegionMetrics}} provided a critical metric for monitoring memory
efficiency. This metric is missing in Apache Ignite 3 and needs to be
implemented to maintain feature parity and provide users with essential memory
monitoring capabilities.
The page fill factor represents the *ratio of space occupied by user and system
data to the total size of all allocated pages* that contain this data. It is
expressed as a value between 0.0 and 1.0.
h3. Purpose and Use Cases
This metric helps determine:
# *Memory Efficiency* - How much of the allocated page memory is actually
being used for storing data versus being wasted as empty space within pages.
# *Fragmentation Detection* - A low fill factor indicates that data pages are
fragmented, meaning there is significant empty space distributed across pages
that cannot be reclaimed.
# *Capacity Planning* - Used to estimate actual data size.
# *Performance Tuning (and memory utilization)* - Low fill factor may indicate
the need for page size adjustment
was:
h3. Background
In Apache Ignite 2, the {{getPagesFillFactor()}} method in
{{DataRegionMetrics}} provided a critical metric for monitoring memory
efficiency. This metric is missing in Apache Ignite 3 and needs to be
implemented to maintain feature parity and provide users with essential memory
monitoring capabilities.
h3. What is Page Fill Factor?
The page fill factor represents the *ratio of space occupied by user and system
data to the total size of all allocated pages* that contain this data. It is
expressed as a value between 0.0 and 1.0.
h3. Purpose and Use Cases
This metric helps determine:
# *Memory Efficiency* - How much of the allocated page memory is actually
being used for storing data versus being wasted as empty space within pages.
# *Fragmentation Detection* - A low fill factor indicates that data pages are
fragmented, meaning there is significant empty space distributed across pages
that cannot be reclaimed.
# *Capacity Planning* - Used to estimate actual data size.
# *Performance Tuning (and memory utilization)* - Low fill factor may indicate
the need for page size adjustment
> Implement getPagesFillFactor metric
> -----------------------------------
>
> Key: IGNITE-27688
> URL: https://issues.apache.org/jira/browse/IGNITE-27688
> Project: Ignite
> Issue Type: Improvement
> Components: storage engines ai3
> Reporter: Vladimir Pligin
> Priority: Major
> Labels: ignite-3
>
> h3. Background
> In Apache Ignite 2, the {{getPagesFillFactor()}} method in
> {{DataRegionMetrics}} provided a critical metric for monitoring memory
> efficiency. This metric is missing in Apache Ignite 3 and needs to be
> implemented to maintain feature parity and provide users with essential
> memory monitoring capabilities.
> The page fill factor represents the *ratio of space occupied by user and
> system data to the total size of all allocated pages* that contain this data.
> It is expressed as a value between 0.0 and 1.0.
> h3. Purpose and Use Cases
> This metric helps determine:
> # *Memory Efficiency* - How much of the allocated page memory is actually
> being used for storing data versus being wasted as empty space within pages.
> # *Fragmentation Detection* - A low fill factor indicates that data pages
> are fragmented, meaning there is significant empty space distributed across
> pages that cannot be reclaimed.
> # *Capacity Planning* - Used to estimate actual data size.
> # *Performance Tuning (and memory utilization)* - Low fill factor may
> indicate the need for page size adjustment
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
