FEATURE: Remove references to convert-document from Technical FAQ about aleph HOT 6 CLOSED

@stchris Says we're done here. Thanks for your help @friendly-wolfbat much appreciated

from aleph.

Hi @friendly-wolfbat, thanks for opening this issue. You are correct, the documentation isn’t up to date in this regard. We do plan to address this as part of a larger overhaul of the technical documentation. But this may take some time, so we should probably address the issue you brought up earlier than that.

from aleph.

Hi @tillprochaska, thanks for responding. If you can clarify on points 2 and 3 briefly (or link me to some code where I can find the answer), I can put together a pull request for this particular issue to correct the documentation.

from aleph.

Hi @friendly-wolfbat , thanks for noticing and for offering to fix this.

1. You're totally right, we missed a few spots where convert-document is still mentioned.
2. We have added a section on scaling workers in general here, so it'd be best to link to that.
3. That's right, that section should stay, because it provides a useful workaround, but the references to the "convert-document service" should probably should just mention "document convert operations" (in ingest-file).

We're very happy to review your contribution as a PR, but otherwise I can take care of these changes, just let me know. Thanks either way!

from aleph.

I tried my hand at the PR. I think one piece that I'm missing is, if a user wishes to disable threading, how many workers should they have relative to the number of cores, and how many ingest-file containers should they have relative to the number of cores?

On a separate note, I see that the installation instructions also say, "[f]or the purpose of scaling workers and getting more predictable performance [...]"--does this mean that disabling threading and having more containers is "better" in terms of performance, or just more predictable?

from aleph.

Thanks @friendly-wolfbat , I'll reply in the PR.

from aleph.