This topic shows you how to change some values in DD Configuration Tools to improve performance and also to understand some of the available settings.
High volume of small incoming jobs
In the case of a setup with the POS set to Push Transactions using DD Mode, and there are many POSs in the setup with high sales volume, this will generate a high volume of incoming jobs to the DD.
As most of the jobs are small, only containing 1 or 2 sales, there is no need to compress these jobs if the network link is stable and fast. On each POS you need to change the Compression setting in the DD Configuration file. This can either be done via the Configuration tool on the POS or by changing the file directly.
If these transactions are to be sent over internet and you have more than two POSs, it is best to have one central DD running within the store to collect these jobs from the POS, so the POS does not have to connect directly to the internet, which will speed up the process on the POS itself.
On the Receving DD at HO that will insert the transactions into the database, you must change the Router Wait value in the System Config tab to a higher value. The default value is 5 seconds, set it to at least 15 seconds or more. This value tells DD how often it should scan the done jobs, clear the memory, and move files from work folder to archive. There will be less clean-up, but the router will have more time to handle the job processing and the processing speed will be increased.
LS Nav 2013 or LS One
When running DD with these systems, DD will connect directly to the SQL Server. This allows DD to have more threads doing more at same time. If DD is to handle a lot of different jobs and job types, it is a good idea to activate the Multi Job Processing option. This will allow two or more different jobs to run at same time.
One DD updating more than one database
If DD is running on a store server and is responsible for updating all the POSs within the store, increase the Data Thread Limit, as this will allow DD to connect to more than one database at same time.