Use patterns
Helix server
usage can affect performance. There are several usage patterns that can
have a direct effect on performance. Since the depot filenames are the
leading portion of the key in several important db.\*
files
(db.rev
, db.revhx
, and db.integed
are among the more notable), the length of paths in the depot filenames
have a direct effect on performance. As the length of paths increase,
performance decreases. It is therefore prudent to discourage the use of
overly-descriptive paths in the depot filenames.
The development methodology can also have a direct effect on
performance. If the development methodology calls for frequent creation
of full branches (perhaps branching for each bug fix), then the amount of
metadata rapidly increases, resulting in more levels within the
db.*
file B-trees. As the number of levels increase, more
key comparisons and I/O requests are required to traverse to the leaf
pages, which will impact performance. Creating full branches also
requires more metadata read and written; the additional metadata read and
written might affect the filesystem cache to the detriment of other
Helix server
tasks. Rather than frequent creation of full branches, it might be
prudent to branch only those files needed for each bug fix, or consider a
development methodology in which multiple bug fixes can occur on the same
branch.
Your search for returned result(s).