Opened 2 years ago

Closed 2 years ago

#2623 closed enhancement (fixed)

I2PSnark: Start with minimum tunnels and then scale according to need

Reported by: Reportage Owned by: zzz
Priority: minor Milestone: 0.9.43
Component: apps/i2psnark Version: 0.9.42
Keywords: I2PSnark, startup, tunnels Cc:
Parent Tickets: Sensitive: no


Currently I2PSnark will start with the configured number of tunnels open, and then after a period of inactivity will reduce the number of tunnels according to usage. This can sometimes result in a delayed build for other service tunnels if a high number of tunnels is configured, and more resource usage than necessary.

Snark should start with the minimum number of tunnels and then scale up according to need, which should result in less resource usage in many cases, and potentially faster build time for other service tunnels at startup in the event Snark tunnels are being built before other tunnels.


Change History (2)

comment:1 Changed 2 years ago by zzz

Status: newopen

This is doable. Only affects those that have manually configured a high number of tunnels. Also, there is logic in the tunnel builder to build pools with no tunnels before building more for a different pool, so it may not affect things that much. Probably would take more time to test than to code.

comment:2 Changed 2 years ago by zzz

Milestone: undecided0.9.43
Resolution: fixed
Status: openclosed
Note: See TracTickets for help on using tickets.