Skip to Content
Menu
Musisz się zarejestrować, aby móc wchodzić w interakcje z tą społecznością.
To pytanie dostało ostrzeżenie
2 Odpowiedzi
11487 Widoki

I am confused about the conf setting. Some say that limit_memory_hard and limit_memory_soft are calculated and write it for per worker. The other says that it calculated and write the total limit of all the workers.

Some of them use:

limit-memory-soft = 2048 X No of worker * 1024 * 1024

The other use:

limit memory soft =  (Total VPS RAM - System RAM - RAM for Odoo) / Total Workers

note:

my spec : 8 Core CPU, 32 GB RAM,  400 GB NVMe Disk Space

so how do I configure this? Please help :(

Awatar
Odrzuć

Hi mike chen,
May i now what method did you used?
limit-memory-soft = 2048 X No of worker * 1024 * 1024 or limit memory soft = (Total VPS RAM - System RAM - RAM for Odoo) / Total Workers?

Najlepsza odpowiedź

Hi,
Yes It is calculated per worker , Maximum allowed virtual memory per worker.

For Odoo 16,
limit-memory-soft = 2048 X No of worker * 1024 * 1024

limit-memory-hard = 2560 X No of worker * 1024 * 1024

2048 and 2560 are standard values for odoo. It will increase/decrease version by version. You can check these values with the -help command when you start the odoo server. 

We add limit_memory_soft and limit_memory_hard parameters in the server configuration file. So we need to define the total limit of all the workers use. That's why we multiply it with the total number of workers.

So the system will manage the Maximum and minimum Total memory allocation limit.

Hope it helps

Awatar
Odrzuć
Autor

I see, so 2048 and 2560 bytes is for per worker, right? And we multiply it by the total number of workers because Odoo will handle the allocation for each workers.

Najlepsza odpowiedź

Contrary to Cybrosys, the documentation states that the figures are for each worker. Thus, shouldn't be multiplied by the quantity of workers

--limit-request--limit-memory-softMaximum allowed virtual memory per worker in bytes. If the limit is exceeded, the worker is killed and recycled at the end of the current request.

Defaults to 2048MiB (2048*1024*1024B).

--limit-memory-hardHard limit on virtual memory in bytes, any worker exceeding the limit will be immediately killed without waiting for the end of the current request processing.

Defaults to 2560MiB (2560*1024*1024B).

--limit-time-cpuPrevents the worker from using more than CPU seconds for each request. If the limit is exceeded, the worker is killed.

Defaults to 60.

--limit-time-realPrevents the worker from taking longer than seconds to process a request. If the limit is exceeded, the worker is killed.



  

Awatar
Odrzuć
Powiązane posty Odpowiedzi Widoki Czynność
0
wrz 23
1746
1
lis 23
2313
1
sie 23
3195
1
kwi 25
1214
2
sty 24
2889