Hi Dataroaring:
For your two questions:
1. exec_mem_limit does not work, and it is not counted in many places:
After this problem is passed through Hook TCMalloc new/delete, all memory
consumption of a query can be counted (if an independent memory allocator is
used in a third-party library, sp
Hi Mingyu,
I agree with you. It's a mistake in figures and I fixed it just now. Thank
you for reminding me!
Best,
Gabriel
On Sat, 12 Mar 2022 at 18:16, 陈明雨 wrote:
> Hi Gabriel:
> As you described in [1], one question is that, we need to start a JVM
> inside BE, instead of using FE to execute th
I agree that `exec_mem_limit` is more easily understood by users as a "memory
limit of a query on a BE".
With the previous behavior, it was difficult and uncontrollable for the user to
understand the relationship between concurrency and query.
However, we may need to be concerned about the fo
Sorry for previous email including a wrong link to discussion on github.
exec_mem_limit is a session variable, which can be set by users. I think we
should define it exactly to make users understood. For example , It is max
memory consumption of a query on a be. If a query consumes memory beyond
e
Hi Gabriel:
As you described in [1], one question is that, we need to start a JVM inside
BE, instead of using FE to execute the UDF.
[1] https://cwiki.apache.org/confluence/display/DORIS/DSIP-001%3A+Java+UDF
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmin...@apache.org
在 2022-03-12
exec_mem_limit is a session variable, which can be set by users. I think we
should define it exactly to make users understood. For example , It is max
memory consumption of a query on a be. If a query consumes memory beyond
exec_mem_limit on a be , it should be failed due to memory allocation.
I a
