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
This would make creating peering maps much simpler. How to add them will be a separate issue. I think they should be stored in the database as relative between unique int64 node IDs, which lower the amount of storage space required (16 bytes per IP, meaning at least 32 bytes per link vs. 8 bytes per ID, meaning only 16 bytes per link).
The text was updated successfully, but these errors were encountered:
This would make creating peering maps much simpler. How to add them will be a separate issue. I think they should be stored in the database as relative between unique
int64
node IDs, which lower the amount of storage space required (16 bytes per IP, meaning at least 32 bytes per link vs. 8 bytes per ID, meaning only 16 bytes per link).The text was updated successfully, but these errors were encountered: