Project

General

Profile

Actions

Bug #31219

closed

Foreman & Katello Memory utilization

Added by prem prakash over 3 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Performance
Target version:
Difficulty:
easy
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

we switched from Katello 3.9 to 3.16.
Here we have a PUMA webserver with 2 workers and 0to 16 thread.

But with the same infrastructure and load, our Memory utilization spiked to 40% from 20%

Does PUMA require more Memory?

Actions #1

Updated by Ian Ballou over 3 years ago

  • Status changed from New to Need more information

Hi prem prakash,

Since we do not know the hardware specs of your Katello server, could you please let us know what those are? Also, please take a look at the tuning profile information at the bottom of this page to ensure your server meets the recommended specs: https://theforeman.org/plugins/katello/nightly/installation/index.html

Actions #2

Updated by prem prakash over 3 years ago

Foreman server has 16CPUs and 64GB RAM
Foreman Tuning = Large
Then changed the following PUMA settings:
Environment=FOREMAN_PUMA_THREADS_MIN=8
Environment=FOREMAN_PUMA_THREADS_MAX=32
Environment=FOREMAN_PUMA_WORKERS=8

Actions #3

Updated by John Mitsch over 3 years ago

Hi Prem Prekesh,

Do you see a particular process using a lot of memory? What is leading you to believe the puma webserver change is what is using up the most memory? Could you provide the output from 'top -o %MEM' This would help us narrow down the concern, pulp 3 services were added in 3.15 and could be affecting resources as well. The output of `systemctl status pulpcore*` would be helpful too.

Actions #4

Updated by Justin Sherrill over 3 years ago

  • Status changed from Need more information to Rejected
  • Target version set to Katello Recycle Bin
  • Triaged changed from No to Yes

Hello!

This issue seems to be more of a support issue than a bug or defect. For more timely responses, please open up a forum post on our support forum: https://community.theforeman.org/c/support/10

I'm going to go ahead and close this now, but if it turns out this is a real bug, we can reopen this issue.

Thanks

Actions

Also available in: Atom PDF