Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#22329 closed enhancement (wontfix)

add support for relays-only / bridges-only onionoo instances

Reported by: cypherpunks Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Onionoo Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The goal is to allow the instance operator to only enable needed functionality for more specific onionoo instances to avoid processing (and downloading) data that the operator does not need.
(or run them separately on dedicated system)

I would envision two new cli parameters:

--relays-only: ignores bridge related documents (does not download or process them)

--bridges-only: ignores relay related documents (does not download or process them)

Child Tickets

Change History (2)

comment:1 Changed 2 years ago by karsten

Resolution: wontfix
Status: newclosed

I'd think that this will be quite confusion for users of such a mirror who don't expect it to leave out relay or bridge details. It also adds overhead to operators going through existing options and to developers maintaining yet some more code. I'd say that if somebody decides to set up an Onionoo instance, they should plan for providing enough resources for processing both relays and bridges. Thanks for the suggestion, but I'll close this as won't fix.

comment:2 in reply to:  1 Changed 2 years ago by cypherpunks

Replying to karsten:

I'd think that this will be quite confusion for users of such a mirror

Since the user is the operator this would not be an issue.

It also adds overhead [...] to developers maintaining yet some more code.

Point taken.

I'd say that if somebody decides to set up an Onionoo instance, they should plan for providing enough resources for processing both relays and bridges.

The point was more that all that BW and CPU cycles to process bridge data is wasted since the instance would _never_ get a request for bridges.

Thanks for the suggestion, but I'll close this as won't fix.

Thanks for your answer.

Last edited 2 years ago by cypherpunks (previous) (diff)
Note: See TracTickets for help on using tickets.