05-23-2024, 02:11 AM
Hi,
I'm using MobileSheets on Windows 11. Local sychronizing libraries takes for me about 1 hour which I consider quite unhandy and unreasonable long.
Out of this ~1 hour it takes about 50min until the 30MB library entries are exchanged between the two PCs and then a few minutes for the real mass data (PDF and MP3).
I observed the following behaviour which is a bit strange to me:
Until the database is completely transfered from Server to Client there is NO progress on the client side. This took in my tests up to 52min.
On the server side it looks only a little better as at least the first two lines from the protocol appear: IP & "Database will be sent to connected device". The progress bar will show 0% on the server until the first song compare happens (after 52min respectively 67min)
After that the the real data is exchanged and the process windows show action. PDF and MP3 transfers work with reasonable speed, considiering that for all files the directory entries are checked again.
I don't mind that the first sync takes a long time, but after only minor (some notes or adding one single song) or even no changes, it takes the same long time for the database exchange. Even a FULL copy (with all MP3 files) on my network could be done in less then 10 min provided a good logic behind it.
Side notes:
I tried as well using the more powerful PC as Client. This has 2 effects
The transfer of the PDF and MP3 files happen with good speed.
Basically I'm doing all the admin work on a desktop with everything on it, and sync to tablets for plaing. On the tablet(s) I'm only doing fine tuning (like notes, correction of song images, changes to playlists). So if after a session I'd like to sync back my notes then one hour is definitely too much.
About the configuration:
I'm doing a two way sync activating:
PC is Master / Tablet is Client
02:49:42 - IP: 192.168.178.36
02:49:51 - Die Datenbank-Datei wird zum verbundenen Gerät gesendet
02:52:29 - 30654464 Bytes der Datei: C:\Users\.....\LocalState\mobilesheets.db erfolgreich gesendet
03:14:22 - Datei erfolgreich empfangen und gespeichert als temp_mobilesheets.db
03:38:55 - Initialisiere Datenbank
03:41:12 - Song XXX wird verglichen
.....
03:44:00 - Die Datenbank-Datei wird zum verbundenen Gerät gesendet
03:44:01 - 14258176 Bytes der Datei: C:\Users\.....\LocalState\temp_mobilesheets.db erfolgreich gesendet
03:44:01 - Datei 1 von 1: C:\Application Data\MobileSheets\xxxx.pdf wird gesendet
03:44:01 - 8309166 Bytes der Datei: C:\Application Data\MobileSheets\xxxx.pdf erfolgreich gesendet
03:44:02 - Die Bibliotheken wurden erfolgreich zusammengeführt. Warten bis der Client fertig ist.
03:44:02 - Die Bibliotheken wurden erfolgreich synchronisiert.
03:44:06 - IP: 192.168.178.36
Comparison table with different Master / Client configuration (with start times after last interaction)
Tablet Master | PC Master | Log
00:00:00 | 00:00:00 | IP: 192.168.178.21
00:00:16 | 00:00:09 | Die Datenbank Datei wird zum verbundenen Gerät gesendet
00:19:27 | 00:02:38 | xxx Bytes der Datei: C:\Users\...\mobilesheets.db erfolgreich gesendet
00:02:36 | 00:21:53 | Datei erfolgreich empfangen und gespeichert als temp_mobilesheets.db
00:02:20 | 00:24:33 | Initialisiere Datenbank
00:42:22 | 00:02:17 | Song XXX wird verglichen
~0:15:00 | ~00:05:00 | End of Song, PDF and other compares (estimated... see Note)
-------------------------------------------------------------------------------------------------
01:07:01 | 00:51:30 | TOTAL (without song compare)
01:22:01 | 00:56:30 | TOTAL (with song compare)
Note: The song compare depends on the number of song changes, MP3 changes and the speed of the CPU and SSD of the master. But as there are user interactions required (at date missmatches) a direct compare is not possible, therefore the estimations
I'm aware, that for a music library this amount of data is big, but for SQL this is just a tiny library. Questions:
Comments are welcome.
Best regards Thomas
I'm using MobileSheets on Windows 11. Local sychronizing libraries takes for me about 1 hour which I consider quite unhandy and unreasonable long.
Out of this ~1 hour it takes about 50min until the 30MB library entries are exchanged between the two PCs and then a few minutes for the real mass data (PDF and MP3).
I observed the following behaviour which is a bit strange to me:
Until the database is completely transfered from Server to Client there is NO progress on the client side. This took in my tests up to 52min.
On the server side it looks only a little better as at least the first two lines from the protocol appear: IP & "Database will be sent to connected device". The progress bar will show 0% on the server until the first song compare happens (after 52min respectively 67min)
After that the the real data is exchanged and the process windows show action. PDF and MP3 transfers work with reasonable speed, considiering that for all files the directory entries are checked again.
I don't mind that the first sync takes a long time, but after only minor (some notes or adding one single song) or even no changes, it takes the same long time for the database exchange. Even a FULL copy (with all MP3 files) on my network could be done in less then 10 min provided a good logic behind it.
Side notes:
I tried as well using the more powerful PC as Client. This has 2 effects
- the time until the first reaction on the Client is then much longer,
- the overall time is even longer (See table below)
The transfer of the PDF and MP3 files happen with good speed.
Basically I'm doing all the admin work on a desktop with everything on it, and sync to tablets for plaing. On the tablet(s) I'm only doing fine tuning (like notes, correction of song images, changes to playlists). So if after a session I'd like to sync back my notes then one hour is definitely too much.
About the configuration:
- 2 x Windows 11
- Server: i14700 / 128MB / SSD HDD
- Typical Client PC: Surface Pro 7 with i10500 / 8MB / SSD HDD
- local WLAN speed >100MBit/s (but actually 1GBit LAN is available as well)
- Size of mobilesheets.db: 30MB
- 6700 songs in the library within 25 PDF files (total about 325 MB, maximum single file 40MB)
- MP3 directory (Server) containing ~150k audio files
- MP3 directory (Client) containing ~6,5k audio files (35GB of MP3 data)
- About 3k songs hold links to audio files (maximum up to 6 links per song)
- Server: CPU, network, RAM, HDD load during sync are all low (3-5min 5% the other time 0%)
- Client: CPU (~10 to 20%), network (0%), RAM (170 to 320MB), HDD (0%) for about 45min/61min
I'm doing a two way sync activating:
- two way sync
- add new song
- sync media data
- sync annotations
- sync midi commands
- sync groups
- sync notes
- Audio data: Sync changes and transmit data
- Behaviour at merge: Use the latest change
- Connect via WIFI
PC is Master / Tablet is Client
02:49:42 - IP: 192.168.178.36
02:49:51 - Die Datenbank-Datei wird zum verbundenen Gerät gesendet
02:52:29 - 30654464 Bytes der Datei: C:\Users\.....\LocalState\mobilesheets.db erfolgreich gesendet
03:14:22 - Datei erfolgreich empfangen und gespeichert als temp_mobilesheets.db
03:38:55 - Initialisiere Datenbank
03:41:12 - Song XXX wird verglichen
.....
03:44:00 - Die Datenbank-Datei wird zum verbundenen Gerät gesendet
03:44:01 - 14258176 Bytes der Datei: C:\Users\.....\LocalState\temp_mobilesheets.db erfolgreich gesendet
03:44:01 - Datei 1 von 1: C:\Application Data\MobileSheets\xxxx.pdf wird gesendet
03:44:01 - 8309166 Bytes der Datei: C:\Application Data\MobileSheets\xxxx.pdf erfolgreich gesendet
03:44:02 - Die Bibliotheken wurden erfolgreich zusammengeführt. Warten bis der Client fertig ist.
03:44:02 - Die Bibliotheken wurden erfolgreich synchronisiert.
03:44:06 - IP: 192.168.178.36
Comparison table with different Master / Client configuration (with start times after last interaction)
Tablet Master | PC Master | Log
00:00:00 | 00:00:00 | IP: 192.168.178.21
00:00:16 | 00:00:09 | Die Datenbank Datei wird zum verbundenen Gerät gesendet
00:19:27 | 00:02:38 | xxx Bytes der Datei: C:\Users\...\mobilesheets.db erfolgreich gesendet
00:02:36 | 00:21:53 | Datei erfolgreich empfangen und gespeichert als temp_mobilesheets.db
00:02:20 | 00:24:33 | Initialisiere Datenbank
00:42:22 | 00:02:17 | Song XXX wird verglichen
~0:15:00 | ~00:05:00 | End of Song, PDF and other compares (estimated... see Note)
-------------------------------------------------------------------------------------------------
01:07:01 | 00:51:30 | TOTAL (without song compare)
01:22:01 | 00:56:30 | TOTAL (with song compare)
Note: The song compare depends on the number of song changes, MP3 changes and the speed of the CPU and SSD of the master. But as there are user interactions required (at date missmatches) a direct compare is not possible, therefore the estimations
I'm aware, that for a music library this amount of data is big, but for SQL this is just a tiny library. Questions:
- Can specific settings improve the timing?
- Could the more powerful PC (Client or Master) do the main part of the compare job?
Comments are welcome.
Best regards Thomas