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
  • #27356

Closed (moved)
Open
Opened Aug 28, 2018 by Karsten Loesing@karsten

Reduce database size and variance of query response times

The ExoneraTor database has grown to 262 GB, and sometimes queries can run for up to a minute or even longer (#17488 (moved)). Both issues are known for years, and they're getting even worse over time as new data gets added.

Sebastian and I discussed possible mitigations over two years ago, and we came up with an improved database schema. Well, Sebastian did the bulk of the work there.

I picked up this work, rebased it to current master, made some fixes, and ran tests on a local database copy. Let's try to merge and deploy this in the next couple of weeks before the code gets old again like last time.

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#27356