Changes between Initial Version and Version 1 of Ticket #24044, comment 72
- Timestamp:
- 07/02/2018 11:36:55 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #24044, comment 72
initial v1 1 1 Adding this index will improve concurrency for all sites, even though the perceived performance gain is minimal. 2 2 3 Doing 50000 row table scans may take only 0.03 seconds - but the machine is using 100% CPU for those 0.03 seconds. CPU that could be used by PHP, the web server, the firewall or any other service running on the server. 3 Doing 50000 row table scans may take only 0.03 seconds - but the machine is using 100% CPU for those 0.03 seconds. CPU that could be used by PHP, the web server, the firewall or any other service running on the server. (This is also wasted energy, in most cases energy generated from fossil fuels for billions of page views generated by WordPress.) 4 4 5 5 Also, in ordinary LRU caching schemes, reading the entire table from disk to do a table scan will cause valuable file system memory caching space to be wasted. 6 7 The argument that most users only have a few hundred rows in the table is invalid - adding this index will be completely unnoticeable for them. 6 8 7 9 The cost of adding the index is minimal/non-existent and the benefits are obvious for those users that do benefit from it.