You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Selvaganesan Govindarajan (JIRA)" <ji...@apache.org> on 2017/05/23 17:48:04 UTC

[jira] [Closed] (TRAFODION-2478) Reduce the number of memory monitoring threads in Trafodion SQL processes

     [ https://issues.apache.org/jira/browse/TRAFODION-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Selvaganesan Govindarajan closed TRAFODION-2478.
------------------------------------------------

> Reduce the number of  memory monitoring threads in Trafodion SQL processes 
> ---------------------------------------------------------------------------
>
>                 Key: TRAFODION-2478
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2478
>             Project: Apache Trafodion
>          Issue Type: Improvement
>          Components: sql-exe
>    Affects Versions: any
>            Reporter: Selvaganesan Govindarajan
>            Assignee: Selvaganesan Govindarajan
>             Fix For: 2.1-incubating
>
>
> A memory monitor thread is created in every SQL process to handle the memory pressure in BMO (Big memory operators).  This has following drawbacks:
> 1) No consistent view of the memory pressure in the node
> 2) Overhead of calculating the memory pressure in every trafodion SQL process.
> Proposal is to move this thread to RMS SSCP process. All SQL processes have access to RMS shared segment. Hence SQL processes can get the view of the memory pressure readily and easily from the shared segment.
> It is also possible to increase the frequency of the memory pressure calculation to get near real tiime picture of the memory pressure.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)