[
https://issues.apache.org/jira/browse/IGNITE-28882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18097513#comment-18097513
]
Ignite TC Bot commented on IGNITE-28882:
----------------------------------------
{panel:title=Branch: [pull/13359/head] Base: [master] : Possible Blockers
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows) 3{color} [[tests 0 TIMEOUT , Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=9214796]]
{color:#d04437}Platform .NET (Windows){color} [[tests 0 TIMEOUT , Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=9214725]]
{color:#d04437}Queries 3{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=9214728]]
* IgniteBinaryCacheQueryTestSuite3:
IndexingCachePartitionLossPolicySelfTest.checkLostPartition[TRANSACTIONAL
READ_ONLY_ALL 2 false 5 true] - Test has low fail rate in base branch 0,0% and
is not flaky
{color:#d04437}Basic 1{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=9214652]]
* IgniteBasicTestSuite: CoreVersionRollingUpgradeTest.testClusterVersionUpgrade
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform C++ CMake (Win x64 / Release){color} [[tests 0
CANCELLED|https://ci2.ignite.apache.org/viewLog.html?buildId=9214721]]
{color:#d04437}Snapshots 2{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=9214753]]
* IgniteSnapshotTestSuite2:
IgniteClusterSnapshotRestoreSelfTest.testCrdLeftDuringCacheStartOnExchangeFinish[encryption=false,
onlyPrimay=false] - Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/13359/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9214797&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9214797
rerunBuildIds=none{color}
> Window Functions - Thread Starvation & Redundant Row Size Calculation
> ---------------------------------------------------------------------
>
> Key: IGNITE-28882
> URL: https://issues.apache.org/jira/browse/IGNITE-28882
> Project: Ignite
> Issue Type: Improvement
> Reporter: Oleg Zinoviev
> Assignee: Oleg Zinoviev
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The current implementation of window functions in the scope of IGNITE-14777
> does not address the following two issues:
> # *Thread starvation risk with large partitions.* When a partition contains
> a large number of rows, the computation thread may get blocked for an
> extended period, causing other execution nodes to experience resource
> starvation.
> # *Redundant row size calculation.* The row size is computed multiple times
> to control memory consumption, which introduces unnecessary overhead.
> h4. Required changes
> * Implement proper release of the execution thread when processing large
> partitions so that other execution nodes do not experience starvation.
> * Send computed rows directly to the downstream node to avoid intermediate
> buffering and redundant calculations.
> * Ensure that the row size is calculated exactly once per row to eliminate
> redundant computations.
> * In streaming mode for window functions, do not include row size
> calculation as part of the computation logic, since in this mode the Node
> does not store rows from upstream.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
