Opened 6 years ago

Last modified 5 years ago

#1609 open defect

peer.failedLookupRate poor when not floodfill

Reported by: dg Owned by: zzz
Priority: minor Milestone: undecided
Component: router/netdb Version: 0.9.20
Keywords: Cc:
Parent Tickets: Sensitive: no


I noticed this on one of my machines.
peer.failedLookupRate is pretty high (3x in some cases) until the machine becomes floodfill.

Maybe this is adversely affecting the non-ff portion of the net?
See attached graph.


Attachments (1)

lookup.png (15.5 KB) - added by dg 6 years ago.
Graph of peer.failedLookupRate showing the behavior.

Download all attachments as: .zip

Change History (3)

Changed 6 years ago by dg

Attachment: lookup.png added

Graph of peer.failedLookupRate showing the behavior.

comment:1 Changed 6 years ago by DjJeshk

I have seen this too. Graph shows about 300-500m when not floodfill, about 100-150m when floodfill. Failed Lookup Rate decreases for me if maximum connection limit is increased.

comment:2 Changed 5 years ago by str4d

Status: newopen
Note: See TracTickets for help on using tickets.