jlaupa commented on issue #11948:
URL: https://github.com/apache/apisix/issues/11948#issuecomment-2732006920

   @shihuncl  @DrJSAnD 
   Well, I finally found the error.
   I will share it with you in case it is your case. good luck.
   
   Apisix in my case was taking as many workers as cores available on the node. 
Which is wrong, it should take from the pod according to the limitation I 
assign.
   The solution was to set a number of workers for my traffic, I have decided 
based on the tests I did that 3 workers is fine. Now (1G ram, at most). If you 
have less memory, lower the workers and try to reuse as much as possible of the 
custom plugins.
   
   The prometheus plugin, even if you set it to 10m, if you exceed this number 
you will only get a warning and it won't really be a problem, but it is noisy.
   How did you check it?
   
   > nproc
   > top
   
   then I saw that there were as many workers as openresty running :D 
   It is advised to have 1 core per worker hence I set 3.
   
   Translated with www.DeepL.com/Translator (free version)


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to