summaryrefslogtreecommitdiff
path: root/test/git/performance/test_odb.py
Commit message (Collapse)AuthorAgeFilesLines
* flattened test folder structure, didn't adjust any file content yetSebastian Thiel2010-11-211-70/+0
|
* 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
* Fixed incorrect use of Blob.data in performance testSebastian Thiel2010-07-131-1/+1
|
* index.add: now uses gitdb.store functionality instead of git-hash-file. The ↵Sebastian Thiel2010-06-211-44/+52
| | | | python version is about as fast, but could support multithreading using async
* commit.create_from_tree now uses pure python implementation, fixed message ↵Sebastian Thiel2010-06-031-3/+3
| | | | | | 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 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