Timeline for get_adjacent_post alternative on a very large db
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:37 | history | edited | CommunityBot |
replaced http://wordpress.stackexchange.com/ with https://wordpress.stackexchange.com/
|
|
| Jun 1, 2013 at 9:20 | comment | added | davidmh |
It's crushing, the total query time in the resquest droped from 123.3ms to 10.6ms. Tomorrow I'll be adding support for the newest and the oldest post, for its previous and next link, respectively. I'm thinking in adding the hashed position as 'endpoint', to return a null and then reset it when a new post gets published.
|
|
| Jun 1, 2013 at 8:09 | comment | added | fuxia♦ |
@davidmh I made an update to store just the ID, and I improved the signature of get_fast_adjacent_post(). It would be nice to see the performance difference from your setup in hard numbers. :)
|
|
| Jun 1, 2013 at 8:06 | history | edited | fuxia♦ | CC BY-SA 3.0 |
fixed a bug, where the complete post was stored in meta
|
| Jun 1, 2013 at 5:55 | comment | added | davidmh | I changed it a bit, it was saving the entire post in the meta, and I added the functions get_fast_previous_post and get_fast_next_post. gist.github.com/davidmh/5689418 | |
| Jun 1, 2013 at 4:33 | vote | accept | davidmh | ||
| Jun 1, 2013 at 2:50 | history | answered | fuxia♦ | CC BY-SA 3.0 |