QUOTE(ticktack @ Nov 6 2022, 09:49)
サイトを落とす事に関してTenboroから明言がありましたか？
すみません、わかりにくいかもしれませんが、私が言いたかったのはページ番号を落とすことで、サイトを落
とすことではありません。ページ番号を廃止しなければならない理由については、以下の引用記事をご覧くだ
さい。
Sorry, in case it was confusing, what I meant was dropping the page number and not the site. See the quoted post below about why the page number has to be discontinued:
QUOTE(Tenboro @ Nov 5 2022, 10:02)
(Not having a page selector is worse than having a page selector / Not having an exact result count is worse than having an exact result count) and this update is therefore a step backwards UI-wise!
Well, no shit. They weren't removed because I thought it would be an improvement, but because with the increasing size of the index, it was getting more and more expensive processing-wise to provide these things, especially considering that the traffic has been significantly increasing as well.
I've seen some people make arguments along the line of "I don't mind waiting three seconds for a search result to appear". There are several problems with this argument:
- First of all, the problem isn't primarily that the user has to wait three seconds for a search result, but that a server is using most of its resources for those three seconds to build said search result - of which the user will probably only look at the first few pages at most.
- Secondly, if it's three seconds for a search today, it'll be six seconds in a couple of years - that is, if it doesn't fail outright due to memory limitations. At this point, the average server CPU load would be above 100% and the site would be effectively unusable.
The site does not have the budget for an additional full rack of high-end servers just to provide the existing functionality with the existing limits, so the options were:
1. Replace the old search engine that uses a naive approach of effectively building the full result for a query (which is necessary for full-range page navigation and exact-ish result counting) with a brand new search engine that is a lot more clever about doing stuff.
2. Put a bandaid on the old search engine by significantly curtailing the maximum size of the search result and/or the range of searchable content.
3. Remove functionalty that was expensive in the old search engine, such as hybrid title/tag searching and comment searching.
With the second option, you would have pages, but there might be a maximum 10 of them with 100 results per page. You'd have exact result counts, but it would be capped to 1000. Many sites use this approach, but if you think for a second that this would cause any less of a shitstorm if we changed to it, I have a bridge to sell you.
With the third option, you would only be able to search for titles or tags, but not both at the same time. Searching would just be all around hampered and unintuitive. See; shitstorm.
Alternatively, you might have a curtailment that only galleries posted in the last couple of years are searchable. Shitstorm.
Alternatively alternatively, those things but with donator-only unlocks and higher limits. Shitstorm.
I went with the first option, which involved three months of active development plus an additional month of testing + optimization, and is, in my opinion, by far the best tradeoff in terms of (server) performance and functionality.
Even if a lot of people disagree, this is a hill I'm willing to die on. And while you are allowed to both disagree and/or dislike change in general, if people keep accusing me of lying to my face about the current state of things and the reasoning for the changes, I'll just start handing out bans to preserve my sanity, so please stop doing that.
As for result counting, I'll put some more effort into providing estimates for various complex results, but this cannot happen until the update has been fully deployed and the old indexing code can be retired.
【良い変態】 日本語でE-Hentai, Japanese Thread
Nov 5 2022, 07:14
