I have a central publisher and several subscribers that are all physically located together and on the same internal network - think of a shop with 7 tills whose local DB replicates to the central DB and then back to the other tills so orders can be looked up on any till.
The replication has been working for several years however the performance has been quite slow and varies vastly between each of the end points - the slowest is showing in the replication monitor as 0.42 rows/second and the fastest is 9.52 rows/second with the others being 1, 3, 4, 6 and 8 rows/second.
I've never quite been able to figure out why there is such a range when all of the end points are physically located next to each other and they all have (from what I can determine) the same configuration. We've eliminated any kind of hardware performance and configuration issues so I'm convinced it is something to do with the replication itself but I don't really understand how to troubleshoot this any further.
How can I see what is causing the slow down on the terminal in question?
This is merge replication where orders are stored locally on the tills, replicated up to the central server and then replicated back down to the other tills so all tills have a copy of all orders.
Tills are running SQLExpress and the replicating central server is SQL Server - all running 2014 versions.