From acc83e27ce907f15596535f788d2feacdfd4af22 Mon Sep 17 00:00:00 2001 From: immber Date: Mon, 14 Jan 2019 10:37:36 -0800 Subject: [PATCH] added TALK_CONCURRENCY to adv config --- docs/source/01-04-planning-architecture.md | 2 ++ docs/source/02-02-advanced-configuration.md | 4 ++++ 2 files changed, 6 insertions(+) diff --git a/docs/source/01-04-planning-architecture.md b/docs/source/01-04-planning-architecture.md index de1cfe803..602222b8f 100644 --- a/docs/source/01-04-planning-architecture.md +++ b/docs/source/01-04-planning-architecture.md @@ -49,6 +49,8 @@ When you are ready to launch your production instance of Talk update your NODE_E Then launch talk with `yarn start` or with the command `NODE_ENV=production ./bin/cli-serve -j -w` +By default Talk will run on a single thread, but you can also run multiple Talk threads on a single application instance by setting the environment variable `TALK_CONCURRENCY`. [See Advanced Configuration](/talk/advanced-configuration/#talk-concurrency) + diff --git a/docs/source/02-02-advanced-configuration.md b/docs/source/02-02-advanced-configuration.md index 49769be0b..1d12d2b47 100644 --- a/docs/source/02-02-advanced-configuration.md +++ b/docs/source/02-02-advanced-configuration.md @@ -23,6 +23,10 @@ otherwise the application will fail to start. Configure the duration for which comment counts are cached for, parsed by [ms](https://www.npmjs.com/package/ms). (Default `1hr`) +## TALK_CONCURRENCY + +This environment variable allows multiple worker processes to be spawned to handle traffic. Defaults to 1 if not set. + ## TALK_DEFAULT_LANG This is a **Build Variable** and must be consumed during build. If using the