summaryrefslogtreecommitdiff
path: root/lib/git/async/channel.py
Commit message (Collapse)AuthorAgeFilesLines
* Removed async from treeSebastian Thiel2010-06-121-338/+0
|
* channel: cleaned up inheritance hierarchy, adding mixing for callback ↵Sebastian Thiel2010-06-121-10/+23
| | | | functionality - previously the callback functionality was bound to channel based readers/writers
* Cleaned up channel design, Reader and Writer bases don't require a channel ↵Sebastian Thiel2010-06-121-23/+116
| | | | | | anymore, but are abstract. Added IteratorReader, implementing the reader interface from an iterator. The implementation moved from the TaskIterator to the channel
* test_task: fixed import error, made all modules from x import * safeSebastian Thiel2010-06-111-0/+3
|
* channel: Changed design to be more logical - a channel now has any amount of ↵Sebastian Thiel2010-06-101-55/+47
| | | | | | readers and writers, a ready is not connected to its writer anymore. This changes the refcounting of course, which is why the auto-cleanup for the pool is currently broken. The benefit of this are faster writes to the channel, reading didn't improve, refcounts should be clearer now
* Channel: Callbacks reviewed - they are now part of Subclasses of the default ↵Sebastian Thiel2010-06-091-0/+51
| | | | channel implementation, one of which is used as base by the Pool Read channel, releasing it of the duty to call these itself. The write channel with callback subclass allows the transformation of the item to be written
* Channel: removed pseudoconstructor, which clearly improves the design and ↵Sebastian Thiel2010-06-091-13/+23
| | | | | | makes it easier to constomize pool: in serial mode, created channels will be serial-only, which brings 15% of performance
* Channel: Read method revised - now it really really doesn't block anymore, ↵Sebastian Thiel2010-06-091-48/+37
| | | | and it runs faster as well, about 2/3 of the performance we have when being in serial mode
* queue: fixed critical bug in the notify method, as it was not at all ↵Sebastian Thiel2010-06-091-1/+0
| | | | | | thread-safe, causing locks to be released multiple times. Now it runs very fast, and very stable apparently. Now its about putting previous features back in, and studying their results, before more complex task graphs can be examined
* workerthread: adjusted to use a blocking queue, it will receive termination ↵Sebastian Thiel2010-06-081-2/+1
| | | | events only with its queue, with boosts performance into brigt green levels
* Its getting better already - intermediate commit before further chaning the ↵Sebastian Thiel2010-06-081-15/+20
| | | | task class
* queue: adjusted queue to be closable ( without own testing yet, except for ↵Sebastian Thiel2010-06-081-30/+14
| | | | the pool which runs it ) - its not yet stable, but should be solvable.
* The new channeldesign actually works, but it also shows that its located at ↵Sebastian Thiel2010-06-081-52/+56
| | | | 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.
* Channel now uses the AsyncQueue, boosting performance by factor 4, its a startSebastian Thiel2010-06-071-2/+2
|
* pool: First version which works as expected in async mode. Its just using a ↵Sebastian Thiel2010-06-071-1/+9
| | | | 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-17/+72
| | | | 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'
* Improved pool design and started rough implementation, top down to learn ↵Sebastian Thiel2010-06-061-12/+37
| | | | 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-051-0/+108
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