Hi,

I am trying to manage user expectations.

What is the expected behavior when multiple users try to sync at the same time.

Is it a consecutive line with users queued up to sync once the previous user is done? Or does MirrorSync work to sync multiple clients concurrently?

Thanks,

ft.

MirrorSync fully supports concurrent syncing. To test this, we spun up 250 virtual machines all running a simultaneous looping script that just ran the sync over and over. Here are the full results of that testing, comparing MirrorSync 2 with MirrorSync 3.

Here is a description of our test methodology:

Times show the average amount of server processing time, in seconds, for each sync operation. Each client computer, running FileMaker Pro, ran in a continuous loop where 5 records out of a 10,000 record table were modified, then synced, then paused for 1 second. Clients were not configured to sync changes from other devices. 
MirrorSync was configured for bidirectional sync (although changes were only made on the client), with serial number primary keys, and XML communication with server. A customization script was configured so that each client only saw its own changes. 
All tests were run on computers hosted with Amazon Web Services, on the same LAN. MirrorSync and FileMaker Server were each installed on a high-end c3.8xlarge server with 32 CPUs and 60 gigabytes of RAM. Client computers were each running on t2.small instances with 2 CPUs and 2 gigabytes of RAM.

Instructions for increasing RAM allocated to MirrorSync can be found here:

http://docs.360works.com/index.php/MirrorSync_4_advanced_topics#OutOfMemoryError

We allocated that much RAM to make sure that it didn't fail with 250 simultaneous syncs. I don't think that it likely made much difference from a performance standpoint.