Previous PageNext Page

3.2.1 Threading Model

The Chili!Soft ASP server can run in either multi-thread or multi-process mode. A multi-threaded server runs one process that starts multiple threads to handle ASP page requests, a multi-process server runs one master process that starts additional processes as needed to handle ASP requests.
 
In most circumstances, we recommend that you run Chili!Soft ASP in multi-process mode. This is the default. You may change the mode by editing the mtengine switch in the [machines] section of the casp.cnfg file. The mode you should choose depends on the specific circumstances of your installation and ASP application. Here is some information that will help you make your choice.
 

Note:

Multi-thread mode is not available when you are running Chili!Soft ASP in a Multi-Machine Chili!Soft ASP

Note:

Multi-process mode is not available on Linux.

3.2.1.1 Stability

Running Chili!Soft ASP in multi-process mode generally provides more stability than running in multi-threaded mode. In multi-threaded mode, a problem with one page can cause problems for all of the users accessing your site. In multi-process mode, a problem with a page or operation will only affect one Chili!Soft ASP process; the other processes will continue to process requests normally
 

3.2.1.2 Speed

For most environments and ASP applications, Chili!Soft ASP will provide better performance running in multi-process mode. However, ASP applications that make heavy use of the Application object will perform better when run multi-threaded mode. This is because in multi-threaded mode, the Application object is stored in memory available to all threads of the single Chili!Soft ASP process. In multi-process mode, accessing the Application object requires inter-process communications, which imposes a slight performance hit.
 

3.2.1.3 Security

A multi-process Chili!Soft ASP server runs under the user account inherited from the Web server process that calls the Chili!Soft ASP server. Because of this, you can use file system permissions to limit Chili!Soft ASP's (and an ASP page's) access to user files, but Chili!Soft ASP configuration files (such as odbc.ini) must be readable by all Web server users.
 
A multi-threaded Chili!Soft ASP server runs under the user account specified in the casp.cnfg file. This user must have read access to all Chili!Soft ASP configuration files, as well as to all individual ASP pages. You can limit access to Chili!Soft ASP configuration files to the specified account that Chili!Soft ASP will run under
 

Copyright © 2000 Chili!Soft

Previous PageTop Of PageNext Page