[ 
https://issues.apache.org/jira/browse/TRAFODION-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862151#comment-15862151
 ] 

ASF GitHub Bot commented on TRAFODION-2478:
-------------------------------------------

GitHub user selvaganesang opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/953

    [TRAFODION-2478] Reduce the number of memory monitoring threads in Tr…

    …afodion SQL processes
    
    The memory monitor thread is now moved to mxsscp process and the collected 
data is
    stored in RMS shared segment. All SQL proceses have access to it.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/selvaganesang/incubator-trafodion 
trafodion-2478

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/953.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #953
    
----
commit 3d7df2d24db818ade2c94d58ed9cd01c1c43f847
Author: selvaganesang <selva.govindara...@esgyn.com>
Date:   2017-02-10T23:56:56Z

    [TRAFODION-2478] Reduce the number of memory monitoring threads in 
Trafodion SQL processes
    
    The memory monitor thread is now moved to mxsscp process and the collected 
data is
    stored in RMS shared segment. All SQL proceses have access to it.

----


> 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
>
> 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)

Reply via email to