~ → loadtest -c 10 --rps 200 http://localhost:8080/deku
[Mon Jun 15 2015 20:48:23 GMT-0700 (PDT)] INFO Requests: 0, requests per second: 0, mean latency: 0 ms
[Mon Jun 15 2015 20:48:28 GMT-0700 (PDT)] INFO Requests: 886, requests per second: 177, mean latency: 0 ms
[Mon Jun 15 2015 20:48:33 GMT-0700 (PDT)] INFO Requests: 1884, requests per second: 200, mean latency: 0 ms
[Mon Jun 15 2015 20:48:38 GMT-0700 (PDT)] INFO Requests: 2884, requests per second: 200, mean latency: 0 ms
[Mon Jun 15 2015 20:48:43 GMT-0700 (PDT)] INFO Requests: 3882, requests per second: 200, mean latency: 0 ms
[Mon Jun 15 2015 20:48:48 GMT-0700 (PDT)] INFO Requests: 4884, requests per second: 200, mean latency: 10 ms
/** @jsx element */
import {element} from 'deku'
var xrange = require('xrange')
function renderNodes (number) {
return xrange(number).map(function (i) {
return (
<div key={ i }>
This is node { i }
</div>
)
})
}
module.exports = (
<div>
{ renderNodes(300) }
</div>
)
I have more of a organization question when using routes. Currently i have a main.js file. I also have a modules folder, and a components folder
I organize it in this fashion: in main.js i import modules, which in turn import components. The route defines which module to load. Minimal exmaple here: http://tabbit.org/MKPhrs
just wondering if this is awful or acceptable. I didn't see a community example with routes, so i gotta ask.