Re: modified for performance: connected versus not connected
Hi,
It just occurred to me, on performance, to deal with the time taken to copy the whole database could be mitigated against.
1) When connected: send each update to the server, and let replication sync it back to one's own client machine. (Just have to be sure the sync happens fast).
2) When disconnected: Copy the DB on the client. Use the copy, and compile SQL updates there. When the connect comes, send up a batch of them to the server, and let them sync. At the same time on the client, revert back to the method in 1, where the slave db is used, and new updates are sent to the server first, then synced with the clients.
Does syncing work fast enough to do it this way?
Subject
Written By
Posted
Re: modified for performance: connected versus not connected
October 29, 2015 10:23PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.