I'm seeing a very specific failbooru with this search. It doesn't happen on page one, although it seems to be slow enough to fall just under the timeout limit, which page 2 then crosses. Albert, any idea what's wrong?
Updated by ZeetherKID77
Posted under General
I'm seeing a very specific failbooru with this search. It doesn't happen on page one, although it seems to be slow enough to fall just under the timeout limit, which page 2 then crosses. Albert, any idea what's wrong?
Updated by ZeetherKID77
葉月 said:
I'm seeing a very specific failbooru with this search. It doesn't happen on page one, although it seems to be slow enough to fall just under the timeout limit, which page 2 then crosses. Albert, any idea what's wrong?
Does it happen on page 3 and other pages as well?
It's timing out on the 29th post: fav:葉月+rating:e&limit=28 fav:葉月+rating:e&limit=29. I'm also getting timeouts on pages 12 through 15 of fav:葉月 -rating:s but strangely not on any of the subsequent pages.
Hmm, fav:shinjidude user:fayli is also failbooruing out on me as well (on the first page this time). Maybe we're just back to that point where long queries die due to traffic growth?
I noticed my-otome fav:raisingk failing for me just yesterday; my-otome fav:albert, too, but the other users I tried all worked.
And also, doing a search for a non-existent user's favorites causes the fav metatag to be ignored instead of just returning no results. Has it always been like that?
This is the query it generates:
SELECT p.* FROM posts p JOIN favorites f ON f.post_id = p.id WHERE true AND p.status <> 'deleted' AND f.user_id = 615 AND p.rating = 'e' ORDER BY f.id DESC offset 20 limit 20;
Playing around with the limit, if you set the limit really high (like 1000) there are no issues. Setting the limit to 1, the database seems to consistently conk out on page 30.
Some explain analyze results: http://pastie.org/1181281