[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #15809 [Onionoo]: onionoo instances disagree on observed and advertised bandwidth

#15809: onionoo instances disagree on observed and advertised bandwidth
-----------------------------+-----------------
     Reporter:  cypherpunks  |      Owner:
         Type:  defect       |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  Onionoo      |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by karsten):

 Here's what happens: onionoo.thecthulhu.com is usually faster at updating
 than onionoo.torproject.org, and updating details documents happens for a
 period of 5 to 15 minutes in the background before the `relays_published`
 timestamp is updated.  As a result, the same request to torproject.org
 might have changed 10 or 20 minutes later even with the same
 `relays_published` timestamp.  If we want to avoid this, we'll have to
 switch to a database and update all documents in a single transaction.
 The current design simply stores documents in the file system, which
 doesn't support such a thing.  I'm aware that this defeats the purpose of
 the `If-Modified-Since` header.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15809#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs