With the cookie_login being logged to the xf_ip table, checking the IP of content or running shared IP checks now takes massively longer.
Since XenForo 1.5.8 (2015-02 or so), Spacebattles has accumulated some 18 million records for cookie_login*. Checking the IP of content often takes unexpectedly long since the registration & confirmation IP are actions of the content_type user instead of just a field off the user table.
Adding the registration/confirmation IP id's directly on a user table would also simplify lookups to have the same efficiency regardless of the table size.
This is perhaps something for XenForo 2.x, but adding a summary table that the shared ip function hits would dramatically reduce the need for bulky indexes on the xf_ip table. With gradually of a day, userid/date/ip/event count would be a vastly simplier structure for displaying IP information in the admincp and running shared ip checks against.
*Pruning this many records will require a script it iterate over records to prevent downtime.
Since XenForo 1.5.8 (2015-02 or so), Spacebattles has accumulated some 18 million records for cookie_login*. Checking the IP of content often takes unexpectedly long since the registration & confirmation IP are actions of the content_type user instead of just a field off the user table.
Adding the registration/confirmation IP id's directly on a user table would also simplify lookups to have the same efficiency regardless of the table size.
This is perhaps something for XenForo 2.x, but adding a summary table that the shared ip function hits would dramatically reduce the need for bulky indexes on the xf_ip table. With gradually of a day, userid/date/ip/event count would be a vastly simplier structure for displaying IP information in the admincp and running shared ip checks against.
*Pruning this many records will require a script it iterate over records to prevent downtime.