geo-replication
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
geo-replication [2021/06/21 20:29] yves |
geo-replication [2021/06/22 15:09] yves |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| {{:geo_transfer_initiate.png?400|}} | {{:geo_transfer_initiate.png?400|}} | ||
| - | You'll notice quickly that the transfer doesn't proceed at the same pace for each PMA.transfer instance. Indeed, that is the purpose of geo-replication in the first place: to make sure that all the slides are available at each geographic location and can be accessed by end-users with the same performance, whether somebody resides in Tokyo, Japan, or Sao Paola, Brazil. | + | You'll notice quickly that the transfer doesn't proceed at the same pace for each PMA.transfer instance. Indeed, that is the purpose of geo-replication in the first place: to make sure that all the slides are available at each geographic location and can be accessed by end-users with the same performance, whether somebody resides in Tokyo, Japan, or Sao Paolo, Brazil. |
| {{:geo_transfer_underway.png?400|}} | {{:geo_transfer_underway.png?400|}} | ||
| Line 33: | Line 33: | ||
| Parallel uploads can be set up in similar fashion as geo-replicated transfers. The following aspects differ: | Parallel uploads can be set up in similar fashion as geo-replicated transfers. The following aspects differ: | ||
| - | * You can still use the site manager to register different target locations. This time, register the same instance of PMA.core multiple times under a different name. Then use the [[bookmarks|Advanced]] tab for each instance to configure different target paths on the same PMA.core. | + | * You can still use the [[about_site_manager|site manager]] to register different target locations. This time, register the same instance of PMA.core multiple times under a different name. Then use the [[bookmarks|Advanced]] tab for each instance to configure different target paths on the same PMA.core. |
| * Your actual transfer should run significantly smoother than under a geo-replication scenario. The reason being that you're connecting to the same PMA.core in each instance of PMA.transfer, and therefore the connection speed in each instance should roughly be the same, too. | * Your actual transfer should run significantly smoother than under a geo-replication scenario. The reason being that you're connecting to the same PMA.core in each instance of PMA.transfer, and therefore the connection speed in each instance should roughly be the same, too. | ||
geo-replication.txt ยท Last modified: 2021/06/22 15:10 by yves
Page Tools
