You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fetching IP information should happen only when needed. Specifically it should occur when a new peer is found that has not been seen before. This could also be optimized further so that it's only fetched when a new IP address is seen.
Current Behavior
Upon restarting the API we are seeing ~45,000 requests for IP data. It seems that for every peer we are re-fetching the IP data unnecessarily.
Possible Solution
Fetch IP data for peers we have not seen before
(Optionally) Fetch iP data for IPs we have not seen before, perhaps by adding a separate db collection for IP data.
The text was updated successfully, but these errors were encountered:
We have now exceeded 100,00 requests today. This is definitely an issue that needs to be investigated and addressed. I would recommend it be prioritized to ensure stability of the system in production.
Expected Behavior
Fetching IP information should happen only when needed. Specifically it should occur when a new peer is found that has not been seen before. This could also be optimized further so that it's only fetched when a new IP address is seen.
Current Behavior
Upon restarting the API we are seeing ~45,000 requests for IP data. It seems that for every peer we are re-fetching the IP data unnecessarily.
Possible Solution
The text was updated successfully, but these errors were encountered: