Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 504
    • Issues 504
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 52
    • Merge requests 52
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #878

Closed
Open
Created Sep 02, 2019 by Tomek Mrugalski@tomek🛰Owner

performance: implement backend statistics

We want to be able to measure the following:

  • looking for reservations took X us,
  • looking for leases took Y us.
  • Z queries per packet were conducted.
  • W total queries performed by backend, average response time was A.
  • possibly stats by query type (getLease4byHWAddr, getLease4ByAddr, etc.)
  • possibly query by SQL type (A number of SELECTs, B number of INSERTs, C number of DELETEs)

This, on its own, wouldn't improve any performance, but it will be an essential tool for assessing other performance improvement proposals.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking