Keep this in mind when estimating the time needed for an initial sync or when much data was changed in the meantime on the primary node. The connection speed varies depending on the hardware and network environment but it does not depend on the size of the repository or SSL use. If no data is changed or transferred, there is no measurable activity. Because the procedure is not multithreaded, it cannot be sped up by using multiple cores. On the standby, you can expect high CPU consumption during the sync process. The additional CPU consumption is low and the extra hard disk and network IO should not produce and performance issues. PerformanceĮnabling TarMK Cold Standby on the primary instance has almost no measurable impact on the performance. All packets are bundled with checksums and when problems with the connection or damaged packets occur, retry mechanisms are triggered. ![]() The data flow is designed to detect and handle connection and network-related problems automatically. The only section available on a standby instance is the Web Console, to facilitate bundle and services configuration. Standby instances are not receiving any type of requests, because they are running in sync only mode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |