DXR Parallel Tree Indexing: Difference between revisions

DXR Parallel Tree Indexing (view source)

55 bytes added , 28 July 2014

Link to request-time-rendering bug.

Confirmed users

574

edits

Revision as of 16:53, 18 July 2014 (view source) Erikrose (talk \| contribs) (Add tree name to the doc.) ← Older edit		Revision as of 19:25, 28 July 2014 (view source) Erikrose (talk \| contribs) (Link to request-time-rendering bug.) Newer edit →
Line 1:		Line 1:
	Once we have request-time rendering in place and no longer have to drag folders full of static HTML around the FS, indexing trees in parallel becomes feasible—something we'll need if we're going to scale up to dozens of trees. (I'm also assuming elasticsearch here.)		Once we have [https://bugzilla.mozilla.org/show_bug.cgi?id=1045183 request-time rendering] in place and no longer have to drag folders full of static HTML around the FS, indexing trees in parallel becomes feasible—something we'll need if we're going to scale up to dozens of trees. (I'm also assuming elasticsearch here.)

	The config file is always going to exist, at least to point to the ES servers. These settings can stay there; changing them will require a WSGI restart:		The config file is always going to exist, at least to point to the ES servers. These settings can stay there; changing them will require a WSGI restart: