| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
incorrect repository
|
|
|
|
| |
run often enough, which is because they intentionally don't have a package initialization file
|
|
|
|
|
|
| |
passed in
test_odb: added more information to the message output
|
|
|
|
| |
The first one is faster, although I would have expected the latter one to be faster
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
python version is about as fast, but could support multithreading using async
|
|
|
|
|
|
| |
was added instead
Adjusted all imports to deal with the changed package names
|
|
|
|
| |
for streams starts to show up, but its not yet there
|
|
|
|
| |
but next there will have to be more through testing
|
|
|
|
| |
multi-threading implementation of all odb functions
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
missing ) and added performance tests which are extremely promising
|
|
|
|
| |
efficiently considering that it copies string buffers all the time
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
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
|
|
tests to work on larger repositories
|