Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #12849

Closed (moved)
(moved)
Open
Created Aug 12, 2014 by Karsten Loesing@karsten

Add web cache to Onionoo's setup

The Onionoo service has become much more "popular" since Orbot started asking Onionoo for relay details a few weeks ago. As of today, Onionoo serves around 160,000 requests per hour to Orbot users. These requests are for roughly 1,000 different documents that are less than 4KB in size and updated once per hour. Up to 159,000 of these requests could be served by a cache.

Would it be possible to add something like Squid in front of Apache, or can we add some other caching mechanism to Apache so that it answers certain requests itself rather than forwarding them to Tomcat?

Is it possible to control this cache by making Tomcat add certain headers to its responses, like a suggested cache lifetime? The Tomcat application knows pretty well when a response is unlikely to change for 15 minutes and when it would be better to invalidate the cache entry after 5 minutes.

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