{"push_id":748931283,"size":4,"distinct_size":0,"ref":"refs/heads/master","head":"1adf6726a887d92403f72639554a49de3984d914","before":"a40e048e0df422fafa53533448c4549353bbbefc","commits":[{"sha":"6a5736fccbb9ec198650e7c812fa21514bf8a2f3","author":{"email":"c0827f05b6b8c60064d48d48e0f0165f96c80be4@gmail.com","name":"Mike Jensen"},"message":"PriorityScheduler: Minor javadoc improvement","distinct":false,"url":"https://api.github.com/repos/threadly/threadly/commits/6a5736fccbb9ec198650e7c812fa21514bf8a2f3"},{"sha":"fb1630d7261d5bffcb1a84b7c4297709a918aa16","author":{"email":"c0827f05b6b8c60064d48d48e0f0165f96c80be4@gmail.com","name":"Mike Jensen"},"message":"Stricter delay time with scheduled task unit tests\n\nAlso removed an extra System.out in another unit test","distinct":false,"url":"https://api.github.com/repos/threadly/threadly/commits/fb1630d7261d5bffcb1a84b7c4297709a918aa16"},{"sha":"3e07c9e757b5ca76c3a9022d7dc5d499209ff017","author":{"email":"c0827f05b6b8c60064d48d48e0f0165f96c80be4@gmail.com","name":"Mike Jensen"},"message":"Reduced clock calls for PriorityScheduler/NoThreadScheduler\n\nThis reduces how many times we need to make system clock calls in scheduling and executing tasks.\nIt also makes the math simpler and more straight forward.\nThe primary goal is a slight increase in performance due to the two items above.\n\nThe overall idea of this is that we work in absolute times (referenced by Clock.accurateForwardProgressingMillis) instead of a delay till execution.\nWe are finally able to remove the ugly thread local class \"ClockWrapper\".  Because we are now working in absolute times rather than delays (where calculations can change if the system clock updates).\n\nThe biggest crappy parts in making a change like this:\n* We can't use the java.util.concurrent.Delayed interface, since this interface focuses on delays it implicitly requires a system clock call.  We now have \"DelayedTaskInterface\" which just has a single call to get the run time (and really is only designed to be used internally).\n* We also need to duplicate the code in ListUtils for now to handle this new interface.  In threadly 5.0.0 when we allow java 8 features we can make ListUtils more generic easily and remove this duplicated code...then it will work with both Delayed and DelayedTaskInterface easily.\n* It makes threadly slightly less standard under the hood.  Should another developer want to jump into the code it provides a small additional difference compared to every other pools I have seen implemented (but we always do it the threadly way...a better way).","distinct":false,"url":"https://api.github.com/repos/threadly/threadly/commits/3e07c9e757b5ca76c3a9022d7dc5d499209ff017"},{"sha":"1adf6726a887d92403f72639554a49de3984d914","author":{"email":"4c572218ea39365d2a907327fb61c6c48ecd65fa@gmail.com","name":"Luke Wahlmeier"},"message":"Merge pull request #155 from jentfoo/reduced_clock_calls\n\nReduced clock calls for PriorityScheduler/NoThreadScheduler","distinct":false,"url":"https://api.github.com/repos/threadly/threadly/commits/1adf6726a887d92403f72639554a49de3984d914"}]}