summaryrefslogtreecommitdiff
path: root/test/git/performance
Commit message (Collapse)AuthorAgeFilesLines
* flattened test folder structure, didn't adjust any file content yetSebastian Thiel2010-11-215-552/+0
|
* fixed performance tests ... again, previously I was just working on an ↵Sebastian Thiel2010-11-201-2/+2
| | | | incorrect repository
* Fixed performance tests which broke in the meanwhile - they definitely don't ↵Sebastian Thiel2010-11-202-3/+3
| | | | run often enough, which is because they intentionally don't have a package initialization file
* Added test to verify the actor type can handle and parse unicode if it is ↵Sebastian Thiel2010-10-151-2/+3
| | | | | | passed in test_odb: added more information to the message output
* Added performance test to compare inst.__class__() vs type(inst)() class. ↵Sebastian Thiel2010-07-141-0/+21
| | | | The first one is faster, although I would have expected the latter one to be faster
* Fixed incorrect use of Blob.data in performance testSebastian Thiel2010-07-131-1/+1
|
* Diff: fixed bug that caused a string to end up as a blob modeSebastian Thiel2010-06-291-1/+1
|
* Fixed performance tests which broke in the course of the sha1-20 byte changesSebastian Thiel2010-06-282-7/+9
|
* Initial frame for implementing read_tree using pure python. As git-read-tree ↵Sebastian Thiel2010-06-221-0/+94
| | | | | | | 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. 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
* index.add: now uses gitdb.store functionality instead of git-hash-file. The ↵Sebastian Thiel2010-06-212-49/+70
| | | | python version is about as fast, but could support multithreading using async
* Removed odb from project, it is now used as a submodule named gitdb, which ↵Sebastian Thiel2010-06-121-9/+4
| | | | | | was added instead Adjusted all imports to deal with the changed package names
* Implemented stream tests, found a bug on the way, slowly a test-framework ↵Sebastian Thiel2010-06-041-11/+2
| | | | for streams starts to show up, but its not yet there
* Fixed implementation after design change to deal with it - all tests run, ↵Sebastian Thiel2010-06-043-7/+22
| | | | but next there will have to be more through testing
* initial version of new odb design to facilitate a channel based ↵Sebastian Thiel2010-06-042-4/+4
| | | | multi-threading implementation of all odb functions
* Fixed compatability issues with python 2.5, made sure all tests runSebastian Thiel2010-06-031-1/+1
|
* commit.create_from_tree now uses pure python implementation, fixed message ↵Sebastian Thiel2010-06-035-13/+62
| | | | | | 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 Added performance tests for serialization, it does about 5k commits per second if writing to tmpfs
* Added performance comparison to cgit ... and yes, git-python is faster :)Sebastian Thiel2010-06-031-7/+60
|
* odb: fixed streamed decompression reader ( specific tests would still be ↵Sebastian Thiel2010-06-031-0/+91
| | | | missing ) and added performance tests which are extremely promising
* odb: implemented loose object streaming, which is impossible to do ↵Sebastian Thiel2010-06-031-0/+44
| | | | efficiently considering that it copies string buffers all the time
* Added first design and frame for object database. In a first step, loose ↵Sebastian Thiel2010-06-021-0/+61
| | | | | | objects will be written using our utilities, and certain object retrieval functionality moves into the GitObjectDatabase which is used by the repo instance Added performance test for object database access, which shows quite respectable tree parsing performance, and okay blob access. Nonetheless, it will be hard to beat the c performance using a pure python implementation, but it can be a nice practice to write it anyway to allow more direct pack manipulations. Some could benefit from the ability to write packs as these can serve as local cache if alternates are used
* commit: redesigned revlist and commit parsing, commits are always retrieved ↵Sebastian Thiel2010-06-021-4/+4
| | | | | | from their object information directly. This is faster, and resolves issues with the rev-list format and empty commit messages Adjusted many tests to go with the changes, as they were still mocked. The mock was removed if necessary and replaced by code that actually executes
* Added performance testing foundation library, reworked existing performance ↵Sebastian Thiel2010-06-022-0/+114
tests to work on larger repositories