Project

General

Profile

Actions

action #160367

closed

openQA Project - coordination #110833: [saga][epic] Scale up: openQA can handle a schedule of 100k jobs with 1k worker instances

openQA Project - coordination #108209: [epic] Reduce load on OSD

After switch to nginx on OSD let's investigate how system performance was impacted

Added by okurz about 1 month ago. Updated about 1 month ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Feature requests
Target version:
Start date:
2024-05-14
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Motivation

After switch to nginx on OSD let's investigate how system performance was impacted. We shouldn't wait too long to still have fresh data with sufficient resolution available.

Acceptance criteria

  • AC1: We know the system performance impact before vs. after based on monitoring data

Suggestions


Related issues 1 (0 open1 closed)

Copied from openQA Project - action #130636: high response times on osd - Try nginx on OSD size:SResolvedmkittler2024-05-17

Actions
Actions #1

Updated by okurz about 1 month ago

  • Copied from action #130636: high response times on osd - Try nginx on OSD size:S added
Actions #2

Updated by okurz about 1 month ago

  • Status changed from New to In Progress
  • Assignee set to okurz
Actions #3

Updated by okurz about 1 month ago

  • Status changed from In Progress to Resolved

Looking at https://monitor.qa.suse.de/d/WebuiDb/webui-summary?orgId=1&from=1714772555160&to=1715761728305 . The time period is 2024-05-04 to 2024-05-08 running apache2 and then 2024-08-09 to 2024-05-15 running ningx, correlating with #130636-22. It's visible as expected that apache data is only available until 2024-05-08. There is no significant change in memory usage, inode or file system usage, system load, cpu usage or http response. The only change seems to be that the ping time slightly increased in that period which is curious. So I guess that means that there is no significant impact of the switch to nginx in neither a negative or positive way. With that we can keep nginx and need no further changes related to system performance impact. Let's see if that helps to prevent http unresponsiveness problems that we want to fix with that.

Actions

Also available in: Atom PDF