summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
...
* workerthread: adjusted to use a blocking queue, it will receive termination ↵Sebastian Thiel2010-06-081-1/+4
| | | | events only with its queue, with boosts performance into brigt green levels
* Revised task deletion works well, adjusted test to be creating new tasks all ↵Sebastian Thiel2010-06-081-22/+29
| | | | the time instead of reusing its own one, it was somewhat hard to manage its state over time and could cause bugs. It works okay, but it occasionally hangs, it appears to be an empty queue, have to gradually put certain things back in, although in the current mode of operation, it should never have empty queues from the pool to the user
* task: now deletes itself once its done - for the test this doesn't change a ↵Sebastian Thiel2010-06-081-1/+4
| | | | thing as the task deletes itself too late - its time for a paradigm change, the task should be deleted with its RPoolChannel or explicitly by the user. The test needs to adapt, and shouldn't assume anything unless the RPoolChannel is gone
* Its getting better already - intermediate commit before further chaning the ↵Sebastian Thiel2010-06-082-7/+14
| | | | task class
* The new channeldesign actually works, but it also shows that its located at ↵Sebastian Thiel2010-06-082-23/+14
| | | | the wrong spot. The channel is nothing more than an adapter allowing to read multiple items from a thread-safe queue, the queue itself though must be 'closable' for writing, or needs something like a writable flag.
* both versions of the async queue still have trouble in certain situations, ↵Sebastian Thiel2010-06-081-5/+9
| | | | at least with my totally overwritten version of the condition - the previous one was somewhat more stable it seems. Nonetheless, this is the fastest version so far
* test implementation of async-queue with everything stripped from it that ↵Sebastian Thiel2010-06-081-0/+6
| | | | didn't seem necessary - its a failure, something is wrong - performance not much better than the original one, its depending on the condition performance actually, which I don't get faster
* introduced a new counter keeping track of the scheduled tasks - this prevent ↵Sebastian Thiel2010-06-071-2/+6
| | | | unnecessary tasks to be scheduled as we keep track of how many items will be produced for the task at hand. This introduces additional locking, but performns well in multithreaded mode. Performance of the master queue is still a huge issue, its currently the limiting factor, as bypassing the master queue in serial moode gives 15x performance, wich is what I would need
* improved testing to test the actual async handling of the pool. there are ↵Sebastian Thiel2010-06-071-5/+24
| | | | 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
* task: Fixed incorrect handling of channel closure. Performance is alright ↵Sebastian Thiel2010-06-071-0/+4
| | | | for up to 2 threads, but 4 are killing the queue
* added high-speed locking facilities, allowing our Queue to be faster, at ↵Sebastian Thiel2010-06-071-7/+13
| | | | 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
* Added task order cache, and a lock to prevent us walking the graph while ↵Sebastian Thiel2010-06-071-9/+31
| | | | | | 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
* pool.consumed_tasks: is now a queue to be thread safe, in preparation for ↵Sebastian Thiel2010-06-071-7/+8
| | | | | | multiple connected pools Reduced waiting time in tests to make them complete faster
* pool: First version which works as expected in async mode. Its just using a ↵Sebastian Thiel2010-06-072-21/+41
| | | | single task for now, but next up are dependent tasks
* channel.read: enhanced to be sure we don't run into non-atomicity issues ↵Sebastian Thiel2010-06-061-1/+1
| | | | 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'
* Plenty of fixes in the chunking routine, made possible by a serialized ↵Sebastian Thiel2010-06-062-23/+149
| | | | chunking test. Next up, actual async processing
* First step of testing the pool - tasks have been separated into a new module ↵Sebastian Thiel2010-06-063-2/+83
| | | | including own tests, their design improved to prepare them for some specifics that would be needed for multiprocessing support
* thread: adjusted worker thread not to provide an output queue anymore - this ↵Sebastian Thiel2010-06-062-4/+82
| | | | | | | is handled by the task system graph: implemented it including test according to the pools requirements pool: implemented set_pool_size
* Improved pool design and started rough implementation, top down to learn ↵Sebastian Thiel2010-06-062-8/+24
| | | | while going. Tests will be written soon for verification, its still quite theoretical
* Renamed mp to async, as this is a much better name for what is actually ↵Sebastian Thiel2010-06-054-3/+3
| | | | 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
* Moved multiprocessing modules into own package, as they in fact have nothing ↵Sebastian Thiel2010-06-054-3/+3
| | | | to do with the object db. If that really works the way I want, it will become an own project, called async
* Initial pool design added, allowing for lazy channel based evaluation of ↵Sebastian Thiel2010-06-053-2/+12
| | | | inter-dependent tasks
* A code donation: Donating a worker thread implementation inclduding tests to ↵Sebastian Thiel2010-06-051-0/+47
| | | | Git-Python. I have the feeling it can do much good here :)
* Added basic channel implementation including testSebastian Thiel2010-06-056-141/+233
| | | | restructured odb tests, they are now in an own module to keep the modules small
* Removed compression flag from IStream and OStream types, as a valid object ↵Sebastian Thiel2010-06-051-6/+49
| | | | | | 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
* Implemented stream tests, found a bug on the way, slowly a test-framework ↵Sebastian Thiel2010-06-043-220/+438
| | | | 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-045-29/+64
| | | | but next there will have to be more through testing
* initial version of new odb design to facilitate a channel based ↵Sebastian Thiel2010-06-044-11/+11
| | | | multi-threading implementation of all odb functions
* Fixed compatability issues with python 2.5, made sure all tests runSebastian Thiel2010-06-032-2/+2
|
* commit.create_from_tree now uses pure python implementation, fixed message ↵Sebastian Thiel2010-06-037-18/+125
| | | | | | 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 frame for object reading, including simple testSebastian Thiel2010-06-021-0/+13
|
* initial version of loose object writing and simple cached object lookup ↵Sebastian Thiel2010-06-021-2/+29
| | | | appears to be working
* Added first design and frame for object database. In a first step, loose ↵Sebastian Thiel2010-06-022-0/+73
| | | | | | 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
* git.cmd: added test for stream section constraint used in git command, found ↵Sebastian Thiel2010-06-021-288/+363
| | | | bug of course which just didn't kick in yet
* commit: redesigned revlist and commit parsing, commits are always retrieved ↵Sebastian Thiel2010-06-024-207/+177
| | | | | | 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/+46
| | | | tests to work on larger repositories
* Added commit-iteration testSebastian Thiel2010-06-021-40/+56
|
* commit: refactored existing code to decode commits from streams - ↵Sebastian Thiel2010-06-024-38/+13
| | | | | | | 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
* commit: initial version of commit_from_tree which could create commit ↵Sebastian Thiel2010-06-021-102/+131
| | | | objects if it could serialize itself
* refs: a Reference can now be created by assigning a commit or object (for ↵Sebastian Thiel2010-05-261-0/+38
| | | | convenience)
* diff: by limiting the splitcount to 5, a subtle bug was introduced as the ↵0.2.0-beta1Sebastian Thiel2010-05-251-1/+15
| | | | | | 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 :)
* Repo: Added comparison operators and hash operator including testSebastian Thiel2010-05-122-5/+14
| | | | Cmd: AutoInterrupt handles boundary cases more gracefully as it can be that the os module suddenly becomes None if the interpreter is going down
* Handle filenames with embedded spaces when generating diffsRick Copeland2010-05-101-0/+1
|
* index.add: added index path rewrite functionality, which allows to store a ↵Sebastian Thiel2010-05-101-0/+30
| | | | | | | 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: added test with some basic assertions for empty repositories theseSebastian Thiel2010-05-102-1/+43
| | | | | | | | 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
* Added additional tz_offset testing in performance test to call it more often.Sebastian Thiel2010-04-302-1/+4
| | | | Fixed test which required to be on master to work - it now uses the HEAD symbolic ref instead.
* Add support for time zone information in tags and commits.Rick Copeland2010-04-271-0/+3
| | | | | | | This commit includes - an update to git.objects.utils:parse_actor_and_date to parse the timezone offset - updates to the git.objects.Commit and git.objects.Tag objects to support *_tz_offset attributes - updates to tests in test.git.test_commit and test.git.test_refs to check for appropriate *_tz_offset attributes
View Lorry Controller Status