2 ms·
The new site's search results are noticeably slower. On search.cpan.org, searching for "cgi" took 90 milliseconds, whereas the new site takes 1.25 seconds. I tr
by combatentropy 8y ago
The new site's search results are noticeably slower. On search.cpan.org, searching for "cgi" took 90 milliseconds, whereas the new site takes 1.25 seconds. I tried several times.
- kbenson 8y agoThey likely don't search the entirely same set of data (that is, cpan's search is likely a subset of metacpan's search). Also, metacpan groups results by package, which cpan returns individual modules (that is, you might have multiple results, one for each module in a package that matches in some manner). Page load speed isn't everything, and the the very quick search suggestions from the metacpan search that on a regular basis get me exactly what I want without a full search page load more than make up for it for me.
- rurban 8y agoBecause the metacpan search is written in java and does not use a fast search engine, like xapian, which does have nice perl5 bindings. Also Elasticsearch uses 10x more RAM.