You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/03/16 08:21:33 UTC
[jira] [Resolved] (PHOENIX-390) About
phoenix.query.spoolThresholdBytes
[ https://issues.apache.org/jira/browse/PHOENIX-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabriel Reid resolved PHOENIX-390.
----------------------------------
Resolution: Fixed
Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.
> About phoenix.query.spoolThresholdBytes
> ---------------------------------------
>
> Key: PHOENIX-390
> URL: https://issues.apache.org/jira/browse/PHOENIX-390
> Project: Phoenix
> Issue Type: Task
> Reporter: Raymond Liu
>
> the doc mentioned that it is 50MB, while actually it is set to 100K by default. Isn't that too small? I found a lot of time is spent in tmp file write and delete in my app.
> Though I tune it to 10MB, it doesn't seems to improve much.
> Btw. the memory chunk for save thresholdBytes of data is created per running task , right? is not per queued task. And only 20% of total memory heap is available for this? so I think 10M might be ok for my 120 threadpoolsize, around 1.2G memory required?
--
This message was sent by Atlassian JIRA
(v6.2#6252)