RTC proxy as Multisite?
How does the RTC proxy or the reverse accelerated proxy server the use case of Global/Distributes Software development?
Is the RTC proxy only a read only proxy which forwards the incoming connections to the central server? Does this only benefit only the checkout scenario ? ie the load ? Does the proxy in any way benefit the commit/deliver scenario? is it faster with the proxy than without it when doing this actions from a remote location over WAN? |
Accepted answer
Putting a proxy in place is primarily to optimize read access, you will incur a slight penalty for adding the extra hop to the server but the trade off is that it *could* respond faster if you hit cache and *could* reduce a request to the jazz server if you hit cache.
When you are performing writes the cache is not used.
> How does the RTC proxy or the reverse accelerated proxy server the use case of Global/Distributes Software development?
Provides you a way to improve read performance for remote users that are performing common operations, i.e. loading the same streams or reloading the same streams often.
> Is the RTC proxy only a read only proxy which forwards the incoming connections to the central server?
Yes.
> Does this only benefit only the checkout scenario ? ie the load ?
This is the primary area, but it can be used to cache other traffic from the server, if you have only configured the connection from your IDE then yes. More generically it is possible for a generic network proxy, WAN accelerator, or any number of data minimizer devices that operate on WAN pipes you can try and cache and proxy all traffic with your Jazz servers.
> Does the proxy in any way benefit the commit/deliver scenario? is it faster with the proxy than without it when doing this actions from a remote location over WAN?
Ultimately a commit is a PUT/POST to the server and will go directly through any intermediate network caching and will need to be transferred over the network so network latency and bandwidth are going to be a factor here. Normally this means a LAN will perform better than the WAN as most WAN connections are throttled or not as fast as the LAN. That being said the Jazz products are highly optimized for WAN use, so while it will be naturally slower over a higer latency or slower connection it is not necessarily Jazz but the network that is the bottleneck at that point.
-Sean
Maxmelbin Neson selected this answer as the correct answer
|
One other answer
here is a blog which might interest you:
https://jazz.net/blog/index.php/2010/10/04/does-rational-team-concert-support-multisite/ |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.