#Nodejs inspector free#
This setting is useful for applications that consume a high amount of memory and want to page out memory to disk occasionally to free up RAM. See documentation to understand what page out means. When set to some value greater than 0, iisnode will page out all its child processes every ‘idlePageOutTimePeriod’ in milliseconds. The default value is 0, which means this feature is disabled. This causes the w3wp to recycle gracefully. If enabled, your node application can connect to a named pipe (environment variable IISNODE_CONTROL_PIPE) and send a “recycle” message. The default value is *.js iisnode.yml recycleSignalEnabled Wild cards are allowed in the file name portion only. Each entry consists of an optional directory name as well as a required file name, which are relative to the directory where the main application entry point is located. Any change to a file causes the application to recycle. Ī semi-colon separated list of files that are watched for changes. In addition to this, for streaming applications, you must also set responseBufferLimit of your iisnode handler to 0. The best to scope this setting only to endpoints that require response streaming (for example, using the element in the web.config)
iisnode offers a configuration setting to override this behavior: to flush a fragment of the response entity body as soon as iisnode receives it from node.exe, you need to set the attribute in web.config to 'true': Įnable the flushing of every fragment of the response entity body adds performance overhead that reduces the throughput of the system by ~5% (as of v0.1.13). The default behavior of IIS is that it buffers response data up to 4 MB before flushing, or until the end of the response, whichever comes first. Enable web sockets on your Azure webapp to use this version. The iisnode-inspector-0.7.3.dll version uses node-inspector-0.7.3 and uses web sockets. The default value is iisnode-inspector-0.7.3.dll. Currently, iisnode-inspector-0.7.3.dll and iisnode-inspector.dll are the only two valid values for this setting. This setting controls what version of node-inspector iisnode uses when debugging your node application. The default value is iisnode, which is relative to the main script directory (directory where main server.js is present) debuggerExtensionDll This setting controls the directory where iisnode logs stdout/stderr. Total Timeout in seconds = (maxNamedPipeConnectionRetry * namedPipeConnectionRetryDelay) / 1000īy default, the total timeout in iisnode on Azure App Service is 200 * 250 ms = 50 seconds. This setting controls the amount of time (in ms) iisnode waits between each retry to send the request to node.exe over the named pipe. Total Timeout in seconds = (maxNamedPipeConnectionRetry * namedPipeConnectionRetryDelay) / 1000 namedPipeConnectionRetryDelay The default value is 200 on Azure App Service. This setting in combination with namedPipeConnectionRetryDelay determines the total timeout of each request within iisnode. This setting controls the maximum number of times iisnode retries making the connection on the named pipe to send the requests to node.exe. You can configure the value depending on how many requests your application receives and how fast your application processes each request. On Azure App Service, the default value is Infinite. This setting controls the maximum number of concurrent requests sent by iisnode to each node.exe. You can set this value to point to your node.exe version. This setting controls the path to the node.exe. To get maximum performance out of your node application, you want to use all vCPUs. Node.exe is single-threaded so one node.exe consumes a maximum of 1 vCPU. The recommended value is 0 for most applications so you can use all of the vCPUs on your machine. You can launch as many node.exes as your VM vCPU count by changing the value to 0. This setting controls the number of node processes that are launched per IIS application. Some of the settings that are useful for your application: nodeProcessCountPerApplication This schema file shows all the settings that you can configure for iisnode. Recommendation is to troubleshoot your app on a non-production setup for example your staging slot and when the issue is fixed, swap your staging slot with your production slot. Use caution when using troubleshooting steps on your production site.
0 kommentar(er)
