Checking for changes ist faster on MacBook

@kilicbatuhan1205 it can be normal depending on a number of variables. Are you on 1.X or 2.X?
Firstly, the network speed will not influence the time it takes to check for changes.
Drive speed, single core performance, background tasks, file system performance, operating system, and drive usage all can influence the time it takes. While I am disappointed that your $3000 machine is running slower than your Macbook, I can think of a few reasons why. The biggest factor in checking for changes in larger projects is the time it takes to check every file in the project. Drive speed and file system speed are the limiting factors. If it's a Windows vs Mac situations, the newer Macs have a better performing file system (APFS vs NTFS) especially for the kind of work Collab does during check for changes. Macbooks also tend to use much faster SSDs than the competition. Both these could be why your Macbook Pro is faster -- you can lookup some benchmarks if you're curious. Your $3000 machine will completely dominate in actual game playing and creation.
Please correct me if any of my assumptions are wrong.

 

@kilicbatuhan1205 It absolutely can when it comes to the kind of operations that Collab does. In checking for changes we read every single file and compute the MD5, then merge that state with what we have saved into the snapshot file. File systems optimised for SSDs will operate better here. The difference between your two machines is a lot higher than I would expect though. I've added it to my list of things to look into when I work on the Collab core. Thank you for your patience!