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

Re: [tor-bugs] #16296 [Onionoo]: Implement lock file in a more robust way

#16296: Implement lock file in a more robust way
-------------------------+--------------------------
     Reporter:  karsten  |      Owner:
         Type:  defect   |     Status:  needs_review
     Priority:  normal   |  Milestone:
    Component:  Onionoo  |    Version:
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+--------------------------

Comment (by karsten):

 This reply doesn't address most of your (valid) points above.

 I was curious about memory usage over time if the hourly updater is not
 started by cron.  That's why I let it run on the Onionoo mirror and added
 another cronjob to measure memory usage:

 {{{
 * * * * * ps ax -o rss,command | grep java >> top-usage
 }}}

 See the [https://trac.torproject.org/projects/tor/attachment/ticket/16296
 /onionoo-mem-usage.png attached graph].  It shows that Java indeed does
 not free most of its memory between runs.  But it also mostly sticks to
 the configured 4 GB threshold and doesn't grow indefinitely.  I'd say that
 while it could behave nicer in theory, this is acceptable behavior.

 But I agree with you that we shouldn't take out the lock file lightly at
 this point.  Needs more thoughts.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16296#comment:5>
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