| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
still inconsistencies that need to be fixed, but it already improved, especially the 4-thread performance which now is as fast as the dual-threaded performance
|
| |
|
|
| |
for up to 2 threads, but 4 are killing the queue
|
| |
|
|
| |
havok - lets call this a safe-state
|
| |
|
|
| |
least in tests, and with multiple threads. There is still an sync bug in regard to closed channels to be fixed, as the Task.set_done handling is incorrecft
|
| |
|
|
|
|
| |
changing tasks
Now processing more items to test performance, in dual-threaded mode as well, and its rather bad, have to figure out the reason for this, probably gil, but queues could help
|
| |
|
|
| |
task.min_count, to fix theoretical option for a deadlock in serial mode, and unnecessary blocking in async mode
|
| |
|
|
|
|
| |
multiple connected pools
Reduced waiting time in tests to make them complete faster
|
| |
|
|
| |
single task for now, but next up are dependent tasks
|
| |
|
|
| |
related to our channel closed flag, which is the only way not to block forever on read(0) channels which were closed by a thread 'in the meanwhile'
|
| |
|
|
| |
chunking test. Next up, actual async processing
|
| |
|
|
| |
including own tests, their design improved to prepare them for some specifics that would be needed for multiprocessing support
|
| |
|
|
|
|
|
| |
is handled by the task system
graph: implemented it including test according to the pools requirements
pool: implemented set_pool_size
|
| |
|
|
| |
while going. Tests will be written soon for verification, its still quite theoretical
|
| |
|
|
| |
going on. The default implementation uses threads, which ends up being nothing more than async, as they are all locked down by internal and the global interpreter lock
|
| |
|
|
| |
to do with the object db. If that really works the way I want, it will become an own project, called async
|
| |
|
|
| |
inter-dependent tasks
|
| |
|
|
| |
Git-Python. I have the feeling it can do much good here :)
|
| |
|
|
| |
restructured odb tests, they are now in an own module to keep the modules small
|
| |
|
|
|
|
| |
will always be compressed if generated by the system ( even future memory db's will compress it )
loose db: implemented direct stream copy, indicated by a sha set in the IStream, including test. This will be the case once Packs are exploded for instance
|
| |
|
|
| |
for streams starts to show up, but its not yet there
|
| |\
| |
| |
| |
| | |
Conflicts:
lib/git/cmd.py
|
| | |
| |
| |
| | |
but next there will have to be more through testing
|
| | |
| |
| |
| | |
multi-threading implementation of all odb functions
|
| | |
| |
| |
| | |
everything. Next is to implement pack-file reading, then alternates which should allow to resolve everything
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
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
|
| | | |
|
| | |
| |
| |
| | |
appears to be working
|
| | |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| | |
bug of course which just didn't kick in yet
|
| | |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| |
| | |
performance is slightly better
git.cmd: added method to provide access to the content stream directly. This is more efficient if large objects are handled, if it is actually used
test.helpers: removed unnecessary code
|
| | |
| |
| |
| | |
objects if it could serialize itself
|
| | |
| |
| |
| |
| |
| | |
make a big difference, but perhaps its smarter about broken pipes.
Adjusted code to selectively strip terminating newline, only if they are there. The previous code would effectively duplicate the string and strip whitespace from both ends even though there was no need for it. Its a bit faster now as the tests proclaim
|
| |/
|
|
| |
easy-to-change class member variable
|
| |
|
|
| |
subproces.Popen invocation. It could be used to pass custom environments, without changing the own one (#26)
|
| |
|
|
| |
the child less cluttered, and make it easier to debug as it will only have the file descriptors we set. It appears to be more stable regarding the stdin-is-closed-but-child-doesn't-realize-this issue
|
| |
|
|
|
|
| |
has unified its way it reads from stdin, now it wants all items to be terminated by a newline usually. Previously, it could have been that it really didn't want to have a termination character when the last item was written to the file. Bumped the minimum requirements to 1.7.0 to be sure it is working as I think it will.
Still, I have to admit that sometime it just appears the closed pipe will not stop git from waiting for more input, at least with the previous implementation
|
| |
|
|
| |
convenience)
|
| |
|
|
| |
containing the lock was removed. This is unlikely to happen in a production envrironment, but may happen during testing, as folders are moved/deleted once the test is complete. Daemons might still be waiting for something, and they should be allowed to terminate instead of waiting for a possibly long time
|
| |
|
|
|
|
| |
newline at the end of the split line was not split away automatically. Added test for this, and the trivial fix
Wow, at least two people reviewd the code, but it slipped through anyway :)
|
| |
|
|
| |
Cmd: AutoInterrupt handles boundary cases more gracefully as it can be that the os module suddenly becomes None if the interpreter is going down
|
| |
|
|
|
|
|
|
| |
and absolute paths were given
Commit.create_from_tree: fixed critical bug that would cause it to create a branch named master by default, instead of the reference actually set ( which is master in many, but not all cases )
- in fact it could be detached as well, we would fail ungracefully although we could assume master then ... although we cant really make the decision
Repo.is_dirty: improved its abiility to deal with empty repositories and a missing head. Weird thing is that the test always worked fine with the previous code, but it didn't work for me in a similar situation without this change at least
|
| | |
|
| |
|
|
|
|
|
| |
different path in the index than the actual one on disk ( from which the object will be created )
Fixed bug the way newlines were handled, which hopefully fixes occasional hangs as well. It works fine with git 1.7.1
Most of the changes are due to the tab-space conversion - its weird once more as I thought it was all in spaces before ... .
|
| |
|
|
|
|
|
|
| |
repo.is_dirty: Will not fail on empty repo ( anymore )
index.entries: will just be empty if the repository is empty
refs: added to_full_path method which can be used to create fully synthetic instances of Reference types, added a test for it
Converted all touched files to spaces, which is why git reports so many changed files. Actually I was thinking every file would use spaces, but apparently not
|
| |
|
|
|
|
|
| |
on lighthouse.
README/intro.rst: added information about the new repository at github
tree: added marker to indicate that submodules would have to be returned there
|
