In January, we announced a beta for our DevOps Dashboard. In February, we released our second beta. Today, we are pleased to announce the availability of our third beta!If you have already registered for the beta, you should have received an email with a link to download beta 3. If you havenot yet registered, head over to our registration page to sign up.
March 20, 2018 Tom Milligan, Senior Area Sales Director
In an ClearCase community, the permanent repository of software artifacts consists of one or more VOBs, which are located on one or more VOB servers.
VOB servers are especially sensitive to memory, because of the performance benefits of caching the VOB database. With more memory, the VOB server can hold more of the database in memory. As a result, it will have to access data from the disk less often, a process that is thousands of times slower than memory access. For the VOB host, the ClearCase Administrator’s Guide recommends a minimum of 128 MB of memory, or half the size of all the VOB databases the host will support, whichever is greater. Heed the advice of the Administrator’s Guide: “Adequate physical memory is the most important factor in VOB performance; increasing the size of a VOB host’s main memory is the easiest (and most cost-effective) way to make VOB access faster and to increase the number of concurrent users without degrading performance.”
March 15, 2018 Tom Milligan, Senior Area Sales Director
Each day, your development team likely performs many check-in or check-out operations from your ClearCase versioned object bases (VOBs).Likewise, if a project has engaged a Continuous Integration process, many software builds may be queued and executed each day.Consider how many ClearCase operations your team performs over the lifetime of a project, and it is easy to see how even a small improvement in the speed of these operations can save a significant amount of time.