| Significance of engine parameters [message #756193] |
Fri, 11 November 2011 07:59  |
Eclipse User |
|
|
|
Hi
Until now we were using the following parameters for engine config
EngineConfig.getAppContext().put(DataEngine.MEMORY_USAGE, DataEngine.MEMORY_USAGE_CONSERVATIVE);
EngineConfig.getAppContext().put(DataEngine.DATA_SET_CACHE_ROW_LIMIT, 30000);
EngineConfig.getAppContext().put(DataEngine.MEMORY_BUFFER_SIZE, 2);
We have done a load test with the above parameters set and were able to run 20 large parallel reports. While having this, there were lot of directories created under /tmp in Linux. Something like below
DataEngine*
DataCache*
Now we have commented these lines. Now we dont see those temporary directories created in /tmp. How will this affect performance.
What are the optimum parameters for high performance
Thanks
[Updated on: Fri, 11 November 2011 08:00] by Moderator |
|
|
|
|
| Re: Significance of engine parameters [message #759975 is a reply to message #759858] |
Wed, 30 November 2011 13:56  |
| Eclipse User |
|
|
|
I thought that setting was for only cubes. I may be wrong, but in any
case I do not know of any issues with it.
Jason
On 11/30/2011 6:07 AM, sam wrote:
> We are getting better results in lower environments with the following
> parameter set.
>
> EngineConfig.getAppContext().put(DataEngine.MEMORY_USAGE,
> DataEngine.MEMORY_USAGE_CONSERVATIVE);
>
> Can we push to production with this setting? Is it safe enough?
>
> Thanks
>
|
|
|
Powered by
FUDForum. Page generated in 0.03645 seconds
Home