Bug 1646118 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(a) increase the timeout seems like the best short-term fix.

I think there's also option (e) which is to move primary indexing to be a taskcluster job that basically produces a tarball that's the indexer output (perhaps pre-codesearch ingestion).  This would likely entail some efforts to compress anything potentially compressible like to pre-gzip HTML that can be served by nginx compression, and to attempt the JSON payloads in the cross-reference database.
(a) increase the timeout seems like the best short-term fix.

I think there's also option (e) which is to move primary indexing to be a taskcluster job that basically produces a tarball that's the indexer output (perhaps pre-codesearch ingestion).  This would likely entail some efforts to compress anything potentially compressible like to pre-gzip HTML that can be served by nginx compression, and to compress the JSON payloads in the cross-reference database (which is not entirely trivial thanks to it being a text file that probably could be a LMDB database or SQLite db using a btree that could compete with binary search).

Back to Bug 1646118 Comment 3