From 4a15449159a01bfde04a668eebdbb93a66072a8d Mon Sep 17 00:00:00 2001 From: Rick Waldron Date: Mon, 31 Aug 2015 14:04:21 -0400 Subject: [PATCH] Update build status icon to svg --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ea12226..1cfdd67 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # temporal -[![Build Status](https://travis-ci.org/rwaldron/temporal.png?branch=master)](https://travis-ci.org/rwaldron/temporal) +[![Build Status](https://travis-ci.org/rwaldron/temporal.svg)](https://travis-ci.org/rwaldron/temporal) Non-blocking, temporal task sequencing. `temporal` does NOT use `setTimeout` or `setInterval`, however there is a cost for using "recursive" `setImmediate` to create an extremely fast, async execution loop. CPU usage is expected to peak when using `temporal`, because the internal ticker needs to execute as fast as possible and as many times per second as possible. It's this speed that allows `temporal` to review the internal schedule for tasks to execute more than once per millisecond, which is needed to create preferential execution cycles for hardware programming.