Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
Onionperf
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • 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.

  • The Tor Project
  • Metrics
  • Onionperf
  • Wiki
  • Home

Home · Changes

Page history
Update home authored Sep 18, 2020 by Karsten Loesing's avatar Karsten Loesing
Hide whitespace changes
Inline Side-by-side
Showing with 5 additions and 5 deletions
+5 -5
  • home.md home.md +5 -5
  • No files found.
home.md
View page @ 5cd67d43
......@@ -6,9 +6,11 @@ Welcome to the OnionPerf wiki! This wiki complements the code repository with do
One of the main goals for developing OnionPerf is to measure long-term performance trends in the Tor network. [Tor Metrics](https://metrics.torproject.org/torperf.html) fetches these measurements once per day and includes them in its performance graphs.
We maintain detailed documentation how we [set up these long-running OnionPerf instances](longterm/setup). These instructions are more specific than the ones in the `README.md` and likely not applicable for all use cases. We wrote this documentation primarily for ourselves, but we share it just in case it's useful for others.
We maintain detailed documentation how we [set up](longterm/setup) these long-running OnionPerf instances. These instructions are more specific than the ones in the `README.md` and likely not applicable for all use cases. We wrote this documentation primarily for ourselves, but we share it just in case it's useful for others.
We also maintain a [table of long-term instances](longterm/data) together with their configurations and data tarballs. We hope that these measurements can be useful to others, maybe even to discover anomalies in the data that we haven't even found yet.
We also maintain a [table](longterm/data) of long-term instances together with their configurations and data tarballs. We hope that these measurements can be useful to others, maybe even to discover anomalies in the data that we haven't even found yet.
We also keep a list of [known artifacts](longterm/artifacts) in long-running OnionPerf measurement data along with likely explanations or open questions to the causes behind these artifacts.
## Experimental measurements
......@@ -16,6 +18,4 @@ We also maintain a [table of long-term instances](longterm/data) together with t
## Research
*OnionPerf has been cited in academic publications including research papers, technical reports, and presentation slides. We maintain a list of such mentions for other researchers and interested parties. (Work in progress.)*
*We also keep a list of known artifacts in OnionPerf measurement data along with likely explanations or open questions to the causes behind these artifacts. (Work in progress.)*
\ No newline at end of file
*OnionPerf has been cited in academic publications including research papers, technical reports, and presentation slides. We maintain a list of such mentions for other researchers and interested parties. (Work in progress.)*
\ No newline at end of file
Clone repository
  • Home
  • longterm
    • artifacts
    • data
    • setup