Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There is another BIG difference here. It has to do with HOW the build gets done. Let me highlight the difference here. </p> <p>If you build from a dedicated build repository workspace, then your build workspace already has a copy of all of the code. When your changes are delivered, and the build is kicked off, then only the changed files (your change set) need to be updated and physically copied from the repository to the build repository workspace. Since most changes are small, this involves the copying of anywhere from 0.1% to 2% of your codebase from the repository.</p> <p>If you build from "the stream", then your build workspace needs to be created (you have to compile somewhere!). So when this is created, your ENTIRE codebase needs to be updated and physically copied from the repository to the build repository workspace. This means retrieving 100% of your codebase from the repository.</p> <p>Each file operation involves a call to discover the needed resource, fetching this resource from the database hosting the repository, and then having the Jazz application provide this source file over the network. It results in a load on the database server, the web server, and the application server. The more you download like this, the more of a load that you put on these components.</p> <p>There are some things you can use to minimize this load on the Jazz infrastructure. Using content caching proxies (using a simple Squid proxy server) can help.</p> <p>For more detail on your options here, and the relative merits of those options, go and read my blog post and whitepaper on Jazz Performance concerns (<a href="http://dtoczala.wordpress.com/2013/02/11/jazz-performance-a-guide-to-better-performance/" rel="nofollow">http://dtoczala.wordpress.com/2013/02/11/jazz-performance-a-guide-to-better-performance/</a>). That article is almost a year old now, but still remains valid. You can also look at the Jazz Deployment Wiki (<a href="https://jazz.net/wiki/bin/view/Deployment/WebHome" rel="nofollow">https://jazz.net/wiki/bin/view/Deployment/WebHome</a>), and check out the sections on performance troubleshooting and performance concerns.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload