So I've decided to hand over the fast-clone npm namespace to a more worthy contender. The fastest deep cloning function on NPM that supports the following types:. Average runtime of various NPM clone libraries on a large complex object loaded from json files of varying sizes ranging from 3.
Fast-clone is a UMD module so you can use it in Node. Got an issue or a feature request? Log it. Pull-requests are also welcome. Skip to content. If true , then the node and its whole subtree, including text that may be in child Text nodes, is also copied.
If false , only the node will be cloned. The subtree, including any text that the node contains, is not cloned. The combination greatly reduces the number of blobs you need to do your work. Sparse-checkout does not reduce the required data transfer for shallow clones. Such repositories are not really available in the open, but are becoming increasingly common for private repositories. If you feel your repository is not represented by our test repositories, then we recommend trying to replicate our experiments yourself.
As can be observed, our test process is not simulating a real life situation where users have different workflows and work on different branches. We are continuing to study these options to get a holistic view of how they change the user experience. A special thanks to Derrick Stolee and our Professional Services team for their efforts and sponsorship of this study! November 10, The new sparse index feature makes it feel like you are working in a small repository when working in a focused portion of a monorepo.
November 4, In October, we experienced one incident resulting in significant impact and degraded state of availability for the GitHub Codespaces service. October 6, Back to GitHub. In this experiment, we aimed to answer the below questions: How fast are the various git clone commands?
Once we have cloned a repository, what kind of impact do future git fetch commands have on the server and client? What impact do full, shallow and partial clones have on a Git server? Will the repository shape and size make any difference in the overall performance?
Experiment design To maximize the repeatability of our experiment, we use open source repositories for our sample data. Test repository characteristics The git-sizer tool measures the size of Git repositories along many dimensions.
Test scenarios We care about the following clone options: Full clones. Here are some common themes we identified that could help you choose the right scenario for your own usage: If you are a developer focused on a single repository, the best approach is to do a full clone and then always perform a full fetch into that clone. Acknowledgements A special thanks to Derrick Stolee and our Professional Services team for their efforts and sponsorship of this study! Tags: Git. Related posts.
November 10, Engineering. November 4, Engineering. Please tell us how this article can be improved: The article is missing important information The article's solutions do not work The article is too complicated The article contains incorrect information The article is out-of-date If you want to provide additional feedback, please include it below.
If you want to provide additional feedback, please include it below. List price.
0コメント