archive-com.com » COM » O » ORCAWARE.COM

Total: 284

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • View source for Server performance tuning for Linux and Unix - SubversionWiki
    be stored in subdirectories that don t grow past a specified size This allows repositories to store many more revisions than can efficiently be stored in one directory Modern filesystems can handle hundreds of thousands of files in a single directory However performance can suffer as the directory index starts to use multiple levels of indirection Some administration tools may also have trouble with very large directories Splitting the revision store into sub directories avoids all these problems The shard size can by adjusted by editing the layout sharded line in db format after svnadmin create but before populating the repository The default is 1000 revisions per subdirectory Non sharded repositories can be loaded into a new sharded repository using svnadmin load or svnsync Optimize write once files on NFS If the repository is on a NFS filesystem then a cache consistency check is made every time a file is opened Since the revision files in a FSFS repository never change it is worthwhile to skip the cache checks on these files The subversion 1 5 repository format store immutable files in specific subdirectories so that this can be done The NFS cache check can be disabled on Linux by passing the nocto option to the mount command note the man page claims this is ignored but it isn t on linux 2 6 You need coherency for some files so the NFS volume is also mounted without the option on a different mount point Symbolic links are made from the cache coherent mount point to the nocto mount for these directories revs and txn protorevs Implementation example not complete just an outline of the key steps stop all servers that can write to the repository sudo mount t nfs nfs server mount point mnt svn o rw nosuid tcp rsize 32768 wsize 32768 sudo mount t nfs nfs server mount point mnt svn nocto o rw nosuid tcp rsize 32768 wsize 32768 nocto actimeo 3600 cd mnt svn repo path mv revs revs nocto mv txn protorevs txn protorevs nocto ln s mnt svn nocto repo path db revs nocto revs ln s mnt svn nocto repo path db txn protorevs nocto txn protorevs start the servers Increase NFS caching timeout On Linux metadata on files from NFS is only kept for a finite period of time This can be changed by passing the actimeo option to the mount command The man page claims the default is 60 seconds but some experimentation suggests it may be higher than that For a nocto mount point this value can be raised to something much larger e g 3600 See the above example Distributing CPU load The subversion communicates with the clients by transmitting differences in state so the CPU load to calculate the difference can be significant By storing the repository on NFS you can have multiple front end FE systems that share the computational load and provide redundancy A network load balancer makes all front ends FEs appear as one

    Original URL path: https://www.orcaware.com/svn/mediawiki/index.php?title=Server_performance_tuning_for_Linux_and_Unix&action=edit (2016-04-24)
    Open archived version from archive


  • Revision history of "Server performance tuning for Linux and Unix" - SubversionWiki
    prev 11 22 15 July 2008 Dchristian Talk contribs 11 781 bytes 789 cur prev 11 06 4 June 2008 Dchristian Talk contribs 10 992 bytes 303 cur prev 10 46 4 June 2008 Dchristian Talk contribs m 10 689 bytes 0 User talk Dchristian moved to Server performance tuning for Linux and Unix Make this widely available cur prev 13 42 30 May 2008 Dchristian Talk contribs 10 689

    Original URL path: https://www.orcaware.com/svn/mediawiki/index.php?title=Server_performance_tuning_for_Linux_and_Unix&action=history (2016-04-24)
    Open archived version from archive

  • Pages that link to "Server performance tuning for Linux and Unix" - SubversionWiki
    Help talk Category Category talk Invert selection Filters Hide transclusions Hide links Hide redirects The following pages link to Server performance tuning for Linux and Unix View previous 50 next 50 20 50 100 250 500 Main Page links User talk Dchristian redirect page links View previous 50 next 50 20 50 100 250 500 Retrieved from https www orcaware com svn wiki Special WhatLinksHere Server performance tuning for Linux

    Original URL path: https://www.orcaware.com/svn/wiki/Special:WhatLinksHere/Server_performance_tuning_for_Linux_and_Unix (2016-04-24)
    Open archived version from archive

  • Server performance tuning for Linux and Unix - SubversionWiki
    grow past a specified size This allows repositories to store many more revisions than can efficiently be stored in one directory Modern filesystems can handle hundreds of thousands of files in a single directory However performance can suffer as the directory index starts to use multiple levels of indirection Some administration tools may also have trouble with very large directories Splitting the revision store into sub directories avoids all these problems The shard size can by adjusted by editing the layout sharded line in db format after svnadmin create but before populating the repository The default is 1000 revisions per subdirectory Non sharded repositories can be loaded into a new sharded repository using svnadmin load or svnsync Optimize write once files on NFS If the repository is on a NFS filesystem then a cache consistency check is made every time a file is opened Since the revision files in a FSFS repository never change it is worthwhile to skip the cache checks on these files The subversion 1 5 repository format store immutable files in specific subdirectories so that this can be done The NFS cache check can be disabled on Linux by passing the nocto option to the mount command note the man page claims this is ignored but it isn t on linux 2 6 You need coherency for some files so the NFS volume is also mounted without the option on a different mount point Symbolic links are made from the cache coherent mount point to the nocto mount for these directories revs and txn protorevs Implementation example not complete just an outline of the key steps stop all servers that can write to the repository sudo mount t nfs nfs server mount point mnt svn o rw nosuid tcp rsize 32768 wsize 32768 sudo mount t nfs nfs server mount point mnt svn nocto o rw nosuid tcp rsize 32768 wsize 32768 nocto actimeo 3600 cd mnt svn repo path mv revs revs nocto mv txn protorevs txn protorevs nocto ln s mnt svn nocto repo path db revs nocto revs ln s mnt svn nocto repo path db txn protorevs nocto txn protorevs start the servers Increase NFS caching timeout On Linux metadata on files from NFS is only kept for a finite period of time This can be changed by passing the actimeo option to the mount command The man page claims the default is 60 seconds but some experimentation suggests it may be higher than that For a nocto mount point this value can be raised to something much larger e g 3600 See the above example Distributing CPU load The subversion communicates with the clients by transmitting differences in state so the CPU load to calculate the difference can be significant By storing the repository on NFS you can have multiple front end FE systems that share the computational load and provide redundancy A network load balancer makes all front ends FEs appear as one server to users The FEs can either

    Original URL path: https://www.orcaware.com/svn/mediawiki/index.php?title=Server_performance_tuning_for_Linux_and_Unix&printable=yes (2016-04-24)
    Open archived version from archive

  • Information for "Server performance tuning for Linux and Unix" - SubversionWiki
    content page Yes Page protection Edit Allow all users infinite Move Allow all users infinite Edit history Page creator Dchristian Talk contribs Date of page creation 13 32 30 May 2008 Latest editor Dchristian Talk contribs Date of latest edit 13 17 15 July 2008 Total number of edits 6 Total number of distinct authors 1 Recent number of edits within past 90 days 0 Recent number of distinct authors

    Original URL path: https://www.orcaware.com/svn/mediawiki/index.php?title=Server_performance_tuning_for_Linux_and_Unix&action=info (2016-04-24)
    Open archived version from archive

  • Svnmerge.py - SubversionWiki
    releases svnmerge py gets shipped with Subversion mostly the way it is when Subversion itself is shipped Thus the trunk version is recommended we believe it to be mostly stable there is a quite extensive testsuite Mailing List A svnmerge mailing list has been established The mailing list is the place to go for information about active development and new features List archives are available at OrcaWare GMANE marc info Nabble Development Patches bugfixes and development of svnmerge are all discussed on the mailing list Patches to svnmerge are also tracked using the svnmerge subcomponent on the Subversion bug tracker To submit a patch or bug report please follow the buddy system as described here but use the svnmerge mailing list Quick Usage Overview Use svnmerge init to initialize merge tracking on a branch directory Use svnmerge avail to review the revisions available for merging Use svnmerge merge to merge in some or all available revisions from other branches Commit the merge changes using svn commit Return to step 2 and repeat Quick tutorials What follows are two quick tutorials for two common usage cases Development branches This tutorial assumes that you are working on a recently created development branch made off the trunk It also assumes that the development branch has never merged changes from the trunk The svnmerge py command works as a pull operation so all commands are run from the development branch working copy This example pulls changes made on the trunk to your development branch Go to the top level directory of a pristine working copy of the branch if you re currently in a working copy directory containing trunk you can switch to the branch using svn switch url path to branch This is your development branch svnmerge py is meant to always operate in this condition so let me repeat top level directory no local modifications Initialize merge tracking support svnmerge py init This command will scan the branch history to find out when the branch was created so to initialize merge tracking support This needs to be done only once for each branch you want to use svnmerge py on You should run this command with in the top level directory of the branch otherwise it won t work as expected The svnmerge py init command added a property to the top level directory Since svnmerge py never does a commit it s your turn to commit that change to the repository You can use the handy automatically generated file svn ci F svnmerge commit message txt rm svnmerge commit message txt Or use your favourite commit message It s time to do a merge To merge everything from the trunk into the branch chdir to the top level of the branch and it s sufficient to do foo branch1 svnmerge py merge or without chdir foo svnmerge py merge branch1 and that s it You will always get the svnmerge commit message txt in the current directory Then review the merge fix any eventual conflict and commit There is a handy commit message listing the logs of all the merged revisions can be quite long which many people find useful According to the svn repository it may be necessary to nav into the directory above the working copy of the branch then name the branch in the svnmerge merge command so the sequence of init tracking merge would be for instance path to dir myworkingcopy svnmerge py init path to dir myworkingcopy svn ci F svnmerge commit message txt path to dir myworkingcopy cd path to dir svnmerge py merge myworkingcopy Repeat the last step whenever you want to merge new changes from the trunk If you want to have a look at what new changes are available to be merged from the trunk do this svnmerge py avail show only the revision numbers svnmerge py avail log show logs of the revisions on the trunk available for merging svnmerge py avail diff show diffs of the revisions on the trunk available for merging Release branches This tutorial assumes that you are working on a recently created release branch made off the trunk in which no changes were previously merged With release branch we mean a branch commonly used to stabilize a release only a few selected changes must be merged from the trunk the others must be ignored The svnmerge py command works as a pull operation so all commands are run from the release branch working copy This example pulls selected changes made on the trunk to your release branch Go to the top level directory of a pristine working copy of the branch svn copy trunk release cd release svnmerge py is meant to always operate in this condition so let me repeat top level directory no local modifications Initialize merge tracking support svnmerge py init This command will scan the branch history to find out when the branch was created so to initialize merge tracking support This needs to be done only once for each branch you want to use svnmerge py on svnmerge py never does a commit so it s your turn You can use the handy automatically generated file svn ci F svnmerge commit message txt rm svnmerge commit message txt Or use your favourite commit message Note however that svnmerge py generates the commit message directly from svn client s output so on Windows it ll have an OEM encoding You need to tell that to svn if your log messages contains non ASCII characters otherwise it ll assume an ANSI encoding and the message may be written incorrectly to the repository Then instead of the command above you should use svn ci encoding IBM850 F svnmerge commit message txt rm svnmerge commit message txt To know the current encoding used in the console one can use the chcp command Review changes available on the trunk to be integrated into the branch svnmerge py avail show only the revision numbers svnmerge py avail

    Original URL path: https://www.orcaware.com/svn/mediawiki/index.php?title=Svnmerge.py&oldid=1776 (2016-04-24)
    Open archived version from archive

  • Talk:Svnmerge.py - SubversionWiki
    been lost See these descriptions http subversion tigris org issues show bug cgi id 2685 http svn collab net repos svn trunk www merge tracking requirements html rename tracking Tobu 08 40 30 March 2007 PDT Retrieved from https www orcaware com svn mediawiki index php title Talk Svnmerge py oldid 1610 Navigation menu Personal tools 81 198 240 36 Talk for this IP address Log in Namespaces Page Discussion

    Original URL path: https://www.orcaware.com/svn/wiki/Talk:Svnmerge.py (2016-04-24)
    Open archived version from archive

  • View source for Svnmerge.py - SubversionWiki
    http www orcaware com pipermail svnmerge OrcaWare http news gmane org gmane comp version control subversion svnmerge devel GMANE http marc info l svnmerge r 1 w 4 marc info http www nabble com Svnmerge py f24192 html Nabble Development Patches bugfixes and development of svnmerge are all discussed on the http www orcaware com mailman listinfo svnmerge mailing list Patches to svnmerge are also tracked using the svnmerge subcomponent on the http subversion tigris org issues buglist cgi Submit query Submit query component subversion subcomponent svnmerge issue status NEW issue status STARTED issue status REOPENED email1 emailtype1 exact emailassigned to1 1 email2 emailtype2 exact emailreporter2 1 issueidtype include issue id changedin votes chfieldfrom chfieldto Now chfieldvalue short desc short desc type substring long desc long desc type substring issue file loc issue file loc type substring status whiteboard status whiteboard type substring keywords keywords type anytokens field0 0 0 noop type0 0 0 noop value0 0 0 cmdtype doit order Reuse same sort as last time Subversion bug tracker To submit a patch or bug report please follow the buddy system as described http subversion tigris org project issues html here but use the http www orcaware com mailman listinfo svnmerge svnmerge mailing list Quick Usage Overview Use svnmerge init to initialize merge tracking on a branch directory Use svnmerge avail to review the revisions available for merging Use svnmerge merge to merge in some or all available revisions from other branches Commit the merge changes using svn commit Return to step 2 and repeat Quick tutorials What follows are two quick tutorials for two common usage cases Development branches This tutorial assumes that you are working on a recently created development branch made off the trunk It also assumes that the development branch has never merged changes from the trunk The svnmerge py command works as a pull operation so all commands are run from the development branch working copy This example pulls changes made on the trunk to your development branch Go to the top level directory of a pristine working copy of the branch if you re currently in a working copy directory containing trunk you can switch to the branch using tt svn switch url path to branch tt This is your development branch svnmerge py is meant to always operate in this condition so let me repeat top level directory no local modifications Initialize merge tracking support pre svnmerge py init pre This command will scan the branch history to find out when the branch was created so to initialize merge tracking support This needs to be done only once for each branch you want to use svnmerge py on You should run this command with in the top level directory of the branch otherwise it won t work as expected The svnmerge py init command added a property to the top level directory Since svnmerge py never does a commit it s your turn to commit that change to the repository You can use the handy automatically generated file pre svn ci F svnmerge commit message txt rm svnmerge commit message txt pre Or use your favourite commit message It s time to do a merge To merge everything from the trunk into the branch chdir to the top level of the branch and it s sufficient to do pre foo branch1 svnmerge py merge pre or without chdir pre foo svnmerge py merge branch1 pre and that s it You will always get the svnmerge commit message txt in the current directory Then review the merge fix any eventual conflict and commit There is a handy commit message listing the logs of all the merged revisions can be quite long which many people find useful According to the svn repository it may be necessary to nav into the directory above the working copy of the branch then name the branch in the svnmerge merge command so the sequence of init tracking merge would be for instance pre path to dir myworkingcopy svnmerge py init path to dir myworkingcopy svn ci F svnmerge commit message txt path to dir myworkingcopy cd path to dir svnmerge py merge myworkingcopy pre Repeat the last step whenever you want to merge new changes from the trunk If you want to have a look at what new changes are available to be merged from the trunk do this pre svnmerge py avail show only the revision numbers svnmerge py avail log show logs of the revisions on the trunk available for merging svnmerge py avail diff show diffs of the revisions on the trunk available for merging pre Release branches This tutorial assumes that you are working on a recently created release branch made off the trunk in which no changes were previously merged With release branch we mean a branch commonly used to stabilize a release only a few selected changes must be merged from the trunk the others must be ignored The svnmerge py command works as a pull operation so all commands are run from the release branch working copy This example pulls selected changes made on the trunk to your release branch Go to the top level directory of a pristine working copy of the branch svn copy trunk release cd release svnmerge py is meant to always operate in this condition so let me repeat top level directory no local modifications Initialize merge tracking support pre svnmerge py init pre This command will scan the branch history to find out when the branch was created so to initialize merge tracking support This needs to be done only once for each branch you want to use svnmerge py on svnmerge py never does a commit so it s your turn You can use the handy automatically generated file pre svn ci F svnmerge commit message txt rm svnmerge commit message txt pre Or use your favourite commit message Note however that svnmerge py generates the commit message directly from svn client s output

    Original URL path: https://www.orcaware.com/svn/mediawiki/index.php?title=Svnmerge.py&action=edit (2016-04-24)
    Open archived version from archive



  •