xinyiZzz opened a new pull request, #12332:
URL: https://github.com/apache/doris/pull/12332

   # Proposed changes
   
   Issue Number: close #xxx
   
   ## Problem summary
   
   In some cases, when the user executes the query for the first time, an error 
of the exceeded mem limit will be reported, and the query will be successful 
again.
   
   This is because when the query is executed for the first time, the memory 
consumed by adding the page cache and other caches is recorded in the query mem 
tracker, and it is hoped that the behavior of multiple queries will be counted.
   
   A temporary solution, remove the hook of scanner thread, test clickbench q13
   1. Before removing the scanner thread hook
   Enable page cache: 3G for the first query, 3G for the tracker; 900M for the 
second query, 900M for the tracker.
   Turn off page cache: 1.9G for the first query, 1.9G for the tracker; 900M 
for the second query, 900M for the tracker
   2. After removing the scanner thread hook
   Enable page cache: 3G for the first query, 1.6G for the tracker; 900M for 
the second query, 900M for the tracker
   Turn off page cache: 1.9G for the first query, 1.6G for the tracker; 900M 
for the second query, 900M for the tracker
   
   TODO, a better solution is to track storage-related memory separately, in 
the scanner thread.
   
   ## Checklist(Required)
   
   1. Does it affect the original behavior: 
       - [ ] Yes
       - [ ] No
       - [ ] I don't know
   2. Has unit tests been added:
       - [ ] Yes
       - [ ] No
       - [ ] No Need
   3. Has document been added or modified:
       - [ ] Yes
       - [ ] No
       - [ ] No Need
   4. Does it need to update dependencies:
       - [ ] Yes
       - [ ] No
   5. Are there any changes that cannot be rolled back:
       - [ ] Yes (If Yes, please explain WHY)
       - [ ] No
   
   ## Further comments
   
   If this is a relatively large or complex change, kick off the discussion at 
[d...@doris.apache.org](mailto:d...@doris.apache.org) by explaining why you 
chose the solution you did and what alternatives you considered, etc...
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org

Reply via email to