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

ASF GitHub Bot commented on ARROW-1795:
---------------------------------------

luchy0120 commented on issue #1303: ARROW-1795: [Plasma] Change evict policy
URL: https://github.com/apache/arrow/pull/1303#issuecomment-344233736
 
 
   @robertnishihara ,  I don't have much knowledge about the design and I can't 
see the whole picture. What I care about is  whether plasma will crash if I put 
it into production and read/write data 1000 times. I'm trying to bring plasma 
to our project . So I want to make sure it will not crash . I don't think it is 
reasonable that if I put data smaller than the initialized amount ,it will 
throw exception saying out-of-memory. As I don't see any doc talking about 
eviction or should I evict data myself , sometimes I 
   need to check some source code in order to  get some knowledge on my own. I 
didn't receive feedback
   of my issue https://issues.apache.org/jira/projects/ARROW/issues/ARROW-1792  
so I search the error and
    try to figure out the reason. I've been working on this for several weeks 
so emotionally I want plasma to be  more stable and more welcoming.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [Plasma C++] change evict policy
> --------------------------------
>
>                 Key: ARROW-1795
>                 URL: https://issues.apache.org/jira/browse/ARROW-1795
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Plasma (C++)
>            Reporter: Lu Qi 
>            Assignee: Lu Qi 
>            Priority: Minor
>              Labels: pull-request-available
>
> case 1.say, we have total free memory 8 G , we have input 5G data, then comes 
> another 6G data, 
> if we choose to evict space 6G , it will throw exception saying that
> no object can be free. This is because we didn't count the 3G remaining free
> space .If we count this remaining 3G , we need to ask only 3G,thus
> we can evict the 5G data and we are still alive . 
> case 2. another situation is :  if we have free memory 10G , we input 1.5G 
> data ,then comes another
> 9G data , if we use  10*20% = 2G data to evict ,then we will crash . In this 
> situation we need to 
> use 9+1.5-10 = 0.5G data to evict  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to