Advanced settings in Web.config

Enable logging for Entity Framework

By default, the logging of Entity Framework operations is discarded and sent to a “black hole”. You can disable this behavior temporarily by editing nlog.config and commenting out the following line:

<logger name="Microsoft.EntityFrameworkCore.*" minlevel="Trace" writeTo="BlackHole"  final="true"/>

Add the key Litium:Data:EnableSensitiveDataLogging to appSettings to log the query parameters (sensitive data) as well.

<appSettings>
    <add key="Litium:Data:EnableSensitiveDataLogging" value="true" />
</appSettings>

This will generate _a lot_ of log entries, many of which will contain sensitive data, so it is recommended to only enable this when troubleshooting an issue locally.

Back to the top

Indexing parameters

There are several available parameters you can set that will affect how the indexing is performed in the background. This can be used when you need more control over how the server resources are utilized. For example, if you find that the indexing uses up all available memory on the server, you can experiment with these settings to help alleviate the situation.

Each of the settings below can be added to the appSettings section.

• IndexJobBatchSize - this controls how many items (base products) the indexer should process at a time. Default value: 100.
• InternalIndexQueueSize - this controls the size of the batch to be written to the indexing file. Default value: 300.
• InternalIndexQueueSizeToBig - this controls how many documents that can be in queue. If the queue is full, the indexer needs to wait for the writer to catch up. Default value: 750.
• IndexUpdateProcessorCount - this sets how many concurrent threads can download and work on creating documents in batch sizes of IndexJobBatchSize. Defaults to the number of processors on the computer.

Back to the top