Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #12655

Closed (moved)
Open
Opened Jul 18, 2014 by Karsten Loesing@karsten

Add performance statistics to Onionoo's servlet

n8fr8 plans to release an Orbot version that queries relay information via Onionoo. There are quite a few Orbots deployed, so this might put some load on Onionoo. We should add some simple performance statistics to Onionoo to detect load problems early.

To start with, let's add statistics for the following request, which is the first request that n8fr8 plans to add to Orbot (it's also the standard request that Atlas and Globe make to show relay details):

https://onionoo.torproject.org/details?lookup=$fingerprint

Some simple metrics to start with might be:

  • Number of requests per 1, 5, 15 minutes
  • Time to parse request, time to build response, time to send response

What I'm not sure about yet is where to store and display these statistics. We could start with heartbeat log messages containing these numbers.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#12655