4 ms·
According to the docs it's using Linux on a smartphone class ARM (AT91SAM9G20) with the ethernet MAC on-chip http://rascalmicro.com/docs/software-guts.html http
by jobytaffey 15y ago
According to the docs it's using Linux on a smartphone class ARM (AT91SAM9G20) with the ethernet MAC on-chip http://rascalmicro.com/docs/software-guts.html http://rascalmicro.com/docs/software-guts.html
The hardware should have no problem maxing out its own network connection. Whether the application software can keep up would be my question.
It's clearly going to perform much better than a nanode http://nanode.eu/ http://nanode.eu/ Which is being pitched as an HTTP enabled sensor node, still relying on Pachube or other cloud services.
But, the Rascal may have enough grunt to run its own services. I wonder how capable it would be of servicing many simultaneous connections? (running Twisted/Node/etc.) Perhaps RAM is the limiting factor?
- pingswept 15y ago(Hi Joby. Why am I acquainted with everyone in this thread?) I think you're right that RAM is the limiting factor. Right now, the uWSGI application server is using ~30% of the CPU and 50% of RAM. Nginx, which is serving the static files, is using very little CPU and maybe 15% of the RAM, which is the same as when Nginx is idle. It's been on the front page of HN for about an hour now, and so far as I can tell, it's surviving fine.