GitPython/test/git/performance/test_utils.py, branch 0.3.2.1-patched

flattened test folder structure, didn't adjust any file content yet

2010-11-21T18:19:04+00:00

Added performance test to compare inst.class() vs type(inst)() class. The first one is faster, although I would have expected the latter one to be faster

2010-07-14T12:27:27+00:00

Initial frame for implementing read_tree using pure python. As git-read-tree can do much more than we can ( and faster assumably ), the .new method is used to create new index instances from up to 3 trees.

2010-06-22T19:23:47+00:00

Implemented multi-tree traversal to facilitate building a stage list more efficiently ( although I am not sure whether it could be faster to use a dictionary together with some intensive lookup ), including test
Added performance to learn how fast certain operations are, and whether one should be preferred over another

Fixed implementation after design change to deal with it - all tests run, but next there will have to be more through testing

2010-06-04T15:22:08+00:00

commit.create_from_tree now uses pure python implementation, fixed message parsing which truncated newlines although it was ilegitimate. Its up to the reader to truncate therse, nowhere in the git code I could find anyone adding newlines to commits where it is written

2010-06-03T21:20:34+00:00

Added performance tests for serialization, it does about 5k commits per second if writing to tmpfs

odb: implemented loose object streaming, which is impossible to do efficiently considering that it copies string buffers all the time

2010-06-03T14:35:35+00:00

GitPython/test/git/performance/test_utils.py, branch 0.3.2.1-patched

flattened test folder structure, didn't adjust any file content yet

Added performance test to compare inst.__class__() vs type(inst)() class. The first one is faster, although I would have expected the latter one to be faster

Initial frame for implementing read_tree using pure python. As git-read-tree can do much more than we can ( and faster assumably ), the .new method is used to create new index instances from up to 3 trees.

Fixed implementation after design change to deal with it - all tests run, but next there will have to be more through testing

commit.create_from_tree now uses pure python implementation, fixed message parsing which truncated newlines although it was ilegitimate. Its up to the reader to truncate therse, nowhere in the git code I could find anyone adding newlines to commits where it is written

odb: implemented loose object streaming, which is impossible to do efficiently considering that it copies string buffers all the time

Added performance test to compare inst.class() vs type(inst)() class. The first one is faster, although I would have expected the latter one to be faster