Versions Compared

Old Version 1

changes.mady.by.user Bram Verniest (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Bram Verniest

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
title
Warning

With the End of Life of CHILI publisher (On Premise) this information is obsolete, and only kept as reference.

CHILI publisher now lives on as GraFx Publisher in the platform of CHILI GraFx


Warning

WARNING - read this first!

Changing the default values for the number of queues on the CHILI server might have a severe impact on your server.

Use a number too low, and the server will not be able to generate as many previews simultaneous as maybe necessary.

Use a number too high, and the server CPU will not be able to follow, causing many failed tasks due to timeouts.

Be VERY careful when changing this setting, and contact support if necessary before doing this change.


Info
title

IMPORTANT

A single CHILI server can only handle so many simultaneous tasks, even when using the maximum allowed number of cores on the CHILI server (16 cores).

When high volume is needed for handling tasks, the only solution will be to buy multiple CHILI servers that can distribute the load.

 


To change the number of queues (and therefor the amount of simultaneous CHILI tasks a server could handle), you will need to follow the following procedure:

  • Stop the 'ChiliService' Windows Service

  • Stop the IIS web server running the CHILI application

  • Go to the CHILI Service installation directory (normally this would be: C:\Program Files(x86)\CHILI Publish\CHILI Service)

  • Take a backup of the config.xml file.

  • Edit the config.xml file and update NumQueueMonitors attribute.

    • Important: more than 20 queues per server are not supported.

  • Start the 'ChiliService' Windows Service

  • Start the IIS web server running the CHILI application

  • Verify if the new configuration was read correctly by the server

    • You can do this by logging into the backoffice and opening the queue service status (Server > Queue and then the Service Status tab). Click on the Refresh button to see the threads.

...