Timeline for Increasing Deployer "Workers" setting based on CPU cores
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 6, 2013 at 15:23 | comment | added | Nuno Linhares♦ | You could try increasing the Windowsize (# of packages the deployer will keep on waiting state) without changing the worker threads, this will at least change when will the deployer start complaining to the transport that it has enough work already... | |
| Nov 6, 2013 at 15:08 | comment | added | Neil | Thanks Nuno. My reason for asking stems from in our case, under "normal" conditions everything is fine, but every so often the client will publish a complete site section of around 1200 pages. I suggested using the Page Publisher Power Tool as this gives more feedback via the queue and doesn't bomb the whole transaction if one thing fails but recently everything seemed to "lock" and I had to restarted Publisher, Transport and Deployer. | |
| Nov 6, 2013 at 15:01 | vote | accept | Neil | ||
| Nov 6, 2013 at 13:12 | history | answered | Nuno Linhares♦ | CC BY-SA 3.0 |