By default - or if 0 is specified for the number of threads - each mHUB engine will use all available processor cores. If running multiple processes simultaneously, or if a single process contains two mHUB engines running simultaneously, then the number of processing threads can be set to a specific value. For example, if the machine has a total of 16 cores, for maximum efficiency two simultaneous processes should be set to use 8 threads each; if both used 16 threads, then efficiency could be significantly decreased due to the 32 threads fighting for limited processor resources.
<debug enabled="false" pathname="C:\Temp\matchIT_Hub_debug.log" truncate="false" />
Should a process that uses mHUB unexpectedly crash, the engine can be configured to create a debug log of all data loaded and all operations performed on the data. This can help identify problematic data, which can then be provided to 360Science for analysis, or cleaned/purged from the original data source.
Once debug mode has been enabled, restart the process. The specified file will be created and written to as data is added and processed. Performance will be impacted because a lot of information will be logged, so debug mode should be enabled only temporarily until the problematic data has been identified. A utility can be provided, upon request, to help analyze the debug log; please contact 360Science for further details.
By default, debug information is appended to the debug file. Enabling truncation will cause the file to be cleared of all data when the engine is started, which will ensure that the file contains only the data leading up to the crash. Please enable truncation before providing a debug file to 360Science for analysis.
mHUB must be initialized with a nationality. Refer to Appendix F for a list of available nationalities.
nationality: Choose the nationality that represents the majority of the data being processed. If processing international data from multiple countries, specify Other. The nationality setting aids with the parsing of all input data.
Further mAPI settings can be configured if necessary. Refer to the Advanced Configuration Guide for full details.