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
Currently, every IP address in a log is checked against the database every time a log page is rendered. If its not in the database, it'll be fetched from ipapi.co. This needs to be optimized since right now it's taking ages (about a minute on my Atom powered machine).
Ideas to test:
put all IPs in a dictionary and use this as lookup table. If an IP is already in there it will no longer be checked. I've tested an implementation of this idea but it didn't improve loading times, probably because it's still hundreds, if not thousands of IPs that need to be checked per log file.
constantly parse logs in the background and add IPs to the database so loading isn't stalled by the ipapi.co lookup. Should improve things, but even a log with already known IPs loads rather slowly.
The text was updated successfully, but these errors were encountered:
Currently, every IP address in a log is checked against the database every time a log page is rendered. If its not in the database, it'll be fetched from ipapi.co. This needs to be optimized since right now it's taking ages (about a minute on my Atom powered machine).
Ideas to test:
put all IPs in a dictionary and use this as lookup table. If an IP is already in there it will no longer be checked. I've tested an implementation of this idea but it didn't improve loading times, probably because it's still hundreds, if not thousands of IPs that need to be checked per log file.
constantly parse logs in the background and add IPs to the database so loading isn't stalled by the ipapi.co lookup. Should improve things, but even a log with already known IPs loads rather slowly.
The text was updated successfully, but these errors were encountered: