Express your wrath digitally
angerlights.com
Express your wrath digitally
1–10 of 17 posts
Re: Express your wrath digitally
#2I signed up for the mailing list last year, and I'm still waiting eagerly for launch! The last blog post on http://pingswept.org/ and https://twitter.com/#!/rascalmicro both look promising.
Re: Express your wrath digitally
#3These lights and the story behind them are interesting, but weathering the flood you'll get if this makes it to the front page is the real story. http://www.rascalmicro.com claims that "The Rascal is powerful enough to handle real web traffic...", and HN has been known to take down much larger hardware. I signed up for the mailing list last year, and I'm still waiting eagerly for launch! The last blog post on http://…
Thanks for the enthusiasm.
I'm watching the logs stream via tail -f right now, and the Rascal is holding up OK. The post is near the bottom of the front page now, and it's handling around 10 hits per second fine. The Rascal is serving both the light control and all the background pages ("what", "story", "technicals") as well. I'm actually more worried about the cable connection to my house than the Rascal. (Eerik put the angerlights in my basement while he moves to California. By the way, he's looking for a job: http://www.linkedin.com/profile/view?id=89147645)
More beta units are on the way-- the hardware beta was successful; software testing is underway.
I'll write up a post-mortem on the HN traffic and put it on the Rascal blog (http://rascalmicro.com/blog/) in a couple days.
Re: Express your wrath digitally
#4Re: Express your wrath digitally
#5I want to make the bulbs die remotely.. Can we do it with a script toggling them on and off in a rapid rate?
If it weren't for the delay, you could hit 300 Hz or so. You could probably even dim the bulbs with PWM if you wanted.
Re: Express your wrath digitally
#6The 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/ 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?
Re: Express your wrath digitally
#7According 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 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/ Which is being pitched as an HTTP enabled sensor…
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.
Re: Express your wrath digitally
#8I want to make the bulbs die remotely.. Can we do it with a script toggling them on and off in a rapid rate?
You're welcome to try. The problem is that the Rascal fetches a new image from the webcam after every click. In order to make sure that the bulbs have turned on (or off) before the image is updated, Eerik added a 1 second delay in the loop. I think this makes it impossible to toggle the bulbs at more than around 0.5 Hz (1 second on, 1 second off). If it weren't for the delay, you could hit 300 Hz or so. You could pro…
Re: Express your wrath digitally
#9Re: Express your wrath digitally
#10EDIT: The problem is your 1280px width declaration in style.css's rascalcontent class. Guessing this will screw up smart phones too.