lukechilds / base64-async
95%
master: 100%

LAST BUILD BRANCH: greenkeeper/coveralls-3.0.7
DEFAULT BRANCH: master
Repo Added
Files 2
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH limit-concurrency
branch: limit-concurrency
CHANGE BRANCH
x

73

push

travis-ci

lukechilds 
Limit how many chunks can be worked in each setImmediate loop

Otherwise it can still block via lots of concurrent jobs. e.g 100 concurrent jobs with a chunk size of 250KB each means that 100 250KB chunks will be worked in each setImmediate loop.

Doesn't seem to make a performance diference. I'm not sure this actualy works...

18 of 20 branches covered (90.0%)

Branch coverage included in aggregate %.

12 of 12 new or added lines in 1 file covered. (100.0%)

51 of 53 relevant lines covered (96.23%)

19.47 hits per line

Relevant lines Covered
53 RELEVANT LINES 51 COVERED LINES
19.47 HITS PER LINE
Source Files on limit-concurrency
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
73 limit-concurrency Limit how many chunks can be worked in each setImmediate loop Otherwise it can still block via lots of concurrent jobs. e.g 100 concurrent jobs with a chunk size of 250KB each means that 100 250KB chunks will be worked in each setImmediate loop. ... push lukechilds travis-ci pending completion  
72 limit-concurrency Limit how many chunks can be worked in each setImmediate loop Otherwise it can still block via lots of concurrent jobs. e.g 100 concurrent jobs with a chunk size of 250KB each means that 100 250KB chunks will be worked in each setImmediate loop. ... push lukechilds travis-ci pending completion  
See All Builds (148)