Project

General

Profile

Actions
Copy link

Bug #9853

closed

Incomplete logging in debug_timming

Added by Nicolas CHARLES almost 8 years ago. Updated almost 8 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Performance and scalability
Target version:
4.0.3
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Most of the cost of compliance computation is not logged on debug_timing, making it hard to detect what is slow and what is not

Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 8 years ago

  • Status changed from New to In progress
Actions
Copy link
 #2

Updated by Nicolas CHARLES almost 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1408
Actions
Copy link
 #3

Updated by Nicolas CHARLES almost 8 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ almost 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.0.3 and 4.1.0~beta3 which were released today.

Actions
Copy link

Also available in: Atom PDF