Opened 6 years ago

Last modified 3 years ago

#3346 new task

Revisit logging design

Reported by: shane Owned by:
Priority: low Milestone: Outstanding Tasks
Component: logging Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by tomek)

This ticket documents a proposed synthetic benchmarking for research purposes.

We use log4cplus where each process logs directly. This was chosen for performance reasons, but we have had a lot of problems getting logging to be free of concurrency problems, in spite of our extra-careful locking.

We should benchmark an approach that sends data to a centralized logging task to see what the performance implications are.

Ideally we should check a few different secondary storage approaches:

  1. Normal spinning disks
  2. Solid-state disks (SSD)
  3. RAM disk (for best-case/worst-case measurement)

We should also check with no concurrent logging, mild concurrent logging, and massively concurrent logging.


Change History (6)

comment:1 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:2 Changed 6 years ago by tomek

  • Milestone changed from Remaining BIND10 tickets to Common Outstanding Tasks
  • Version set to git

comment:3 Changed 4 years ago by tomek

  • Milestone changed from Common Outstanding Tasks to DHCP Outstanding Tasks

comment:4 Changed 4 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

comment:5 Changed 3 years ago by tomek

  • Description modified (diff)
  • Priority changed from medium to low

comment:6 Changed 3 years ago by tomek

We haven't heard any complaints from users about Kea logging experiencing any concurrency problems. That doesn't prove anything, it simply is a data point sufficient to lower priority of this work.

Note: See TracTickets for help on using tickets.