Change Details

What cyberbot does seems a legitimate query, but it could do the same queries in a slightly different pattern being probably 100x faster, and taking much less resources. I can see it executing: ``` SELECT * FROM externallinks LIMIT 107115000,15000 ``` Which is taking minutes to execute, as it will be reading 100M rows. This is a big no for paging in MySQL, as it takes as much time as scanning the whole table, while only retrieving 15K records. If the aim is to do a full externallinks scan, there is a nice el_id index to iterate, e.g.: ``` SELECT * FROM externallinks WHERE el_id > 107115000 ORDER BY el_id LIMIT 15000; ``` Which takes only 0.05 sec., (6000x faster) and you can scan the full table in less than a few minutes. Please show me your code and I will fix it for you, and you will never have to wait again- plus you will make more resources available for other users.

What cyberbot does seems a legitimate query, but it could do the same queries in a slightly different pattern being probably 100x faster, and taking much less resources. I can see it executing: ``` SELECT * FROM externallinks LIMIT 107115000,15000 ``` Which is taking minutes to execute, as it will be reading 100M rows. This is a big no for paging in MySQL, as it takes as much time as scanning the whole table, while only retrieving 15K records. If the aim is to do a full externallinks scan, there is a nice el_id index to iterate, e.g.: ``` SELECT * FROM externallinks WHERE el_id > 107115000 ORDER BY el_id LIMIT 15000; ``` (then you use the last returned id to do the next query, until no rows are returned). Which takes only 0.05 sec., (6000x faster) and you can scan the full table in less than a few minutes. Please show me your code and I will fix it for you, and you will never have to wait again- plus you will make more resources available for other users.

What cyberbot does seems a legitimate query, but it could do the same queries in a slightly different pattern being probably 100x faster, and taking much less resources. I can see it executing: ``` SELECT * FROM externallinks LIMIT 107115000,15000 ``` Which is taking minutes to execute, as it will be reading 100M rows. This is a big no for paging in MySQL, as it takes as much time as scanning the whole table, while only retrieving 15K records. If the aim is to do a full externallinks scan, there is a nice el_id index to iterate, e.g.: ``` SELECT * FROM externallinks WHERE el_id > 107115000 ORDER BY el_id LIMIT 15000; ``` (then you use the last returned id to do the next query, until no rows are returned). Which takes only 0.05 sec., (6000x faster) and you can scan the full table in less than a few minutes. Please show me your code and I will fix it for you, and you will never have to wait again- plus you will make more resources available for other users.