All the mapping defined are formed and stored in the global file entries of UMA and UMA can create from 1 ~ 10 threads to traverse the global file entries. More concurrent threads would be useful if there are a mixture of big-sized and small-sized files because when one thread is busy hashing a big file, the next available thread can continue with the subsequent file entries. The end result would be all the small-sized files would be processed and transferred sooner without having to get stuck waiting for one thread to hash big-sized files. All concurrent threads run together and scan the file list in a sequence. If you look at the diagram below, the 4 concurrent threads would take turn scanning all the files in the monitoring list. If thread 1 is busy scanning a big file, the next available thread would scan the next file.

If all the files are small in size, then the speed difference is minimal.
If they have configured the alert setting like below:

they can retrieve the files from C:\Program Files\e-Lock Corporation\WebAlarm Agent\Settings\Tamper\