Actual behavior:

Expected behavior:

Seems like the issue is caused by some overly-strict overflow: hidden styles on the containing blocks. Maybe it would be bet

At present we can run the load generator for a set amount of time or a certain number of requests.
I would like to a mode --reconnetRequests=1000 where fortio client will reconnect after 1000 requests.

Use case: We are testing SDS cert rotation using an https fortio client (std client).
For cert rotation to be exercised fortio should reconnect periodically to fetch the new cert.
In

We should make better documentation about how to use the tool. I think it could be similar to talk presented on Cracows meetup (slides: https://speakerdeck.com/michalslaski/exploring-beam-based-systems-with-erlang-dot-pl) Showing possible workflow.

this is for RuntimeTools/appmetrics#408

only happens when using .attach() method. Seems we need to require appmetics first then pass it into the constructor for the dashboard

var appmetrics = require('appmetrics')
var dash = require('appmetrics-dash')
var express = require("express");
var app = express();
dash.attach({appmetrics:appmetrics});

docs change r

Raising on behalf of @seabaylea
At the moment the documentation in the README is sufficient to run either SM-dash or SM-prometheus. The only documented constructors in the example are the convenience ones, so each will create their own Router and pass it to Kitura. This means the last one created wins, and will block the other from displaying.

Documentation needs to show how to create and pas

OpenCL examples are not working at all

surface

plotting

plot3
![plot3_opencl](https://cloud.githubusercontent.com/assets/364829/16026084/bab84c42-

Bug: analyticalmonk/Rperform#44

Reference: ropensci/git2r#312