Global Feed Post Login
Replying to Avatar Ingwie Phoenix (aka. birb)

Next, I want to improve my i2p speeds. Right now, my relay is... sometimes reachable. Not very reliable o.o And even then, it's ridiculously slow...

---

# time curl -x socks5h://127.0.0.1:4447 -Lv 5rx5xnftplvtn2ekh6pc33drl3wtdevouazmig3e656javcnyfla.b32.i2p

* Trying 127.0.0.1:4447...

* SOCKS5 connect to 5rx5xnftplvtn2ekh6pc33drl3wtdevouazmig3e656javcnyfla.b32.i2p:80 (remotely resolved)

(...snip...)

real 0m9.786s

user 0m0.000s

sys 0m0.010s

# time curl -Lv 100.64.0.2:7777

* Trying 100.64.0.2:7777...

* Connected to 100.64.0.2 (100.64.0.2) port 7777 (#0)

(...snip...)

real 0m0.071s

user 0m0.000s

sys 0m0.014s

---

(Tested from a remote server where 100.64.0.2 is the same server running the relay.)

The time difference is... a lot. o.o

Avatar
Toof 2y ago

If you are using #i2pd, you can mess with increasing tunnels and/or decreasing hops. This has helped decrease load times for me.

{inbound,outbound}.quantity = [1-16]

{inbound,outbound}.length = [1-8]

https://i2pd.readthedocs.io/en/latest/user-guide/tunnels/#i2cp-parameters

Reply to this note

Please Login to reply.

Discussion

No replies yet.