Ha yeah - we opened up a port in iptables for this so we don't have to ssh tunnel in to see stats. Obviously, if you're concerned about exposing numbers, you can view via an ssh tunnel instead of opening a port.

I see you are using SVG to render the charts. What are your thoughts on SVG vs Canvas for these types of apps?

Not these guys, but doing realtime viz of signals.

We've switched over to a minimalist canvas renderer--if you don't need interactivity or styling, and instead just "draw me as much as you can as fast as you can, damnit.", we hope it's the way to go.

I've been playing around (http://yield.io) with Flot, which uses canvas and rendering speed seems pretty good, but resizing gets a bit wonky when there are multiple canvas elements on a page.

Yeah, we started with Flotr2...too many graphs on a page (with thousands of datapoints per graph) brings Chrome to its knees, even with auto margins and whatnot turned off.

EDIT: Very clean site! I like your style. :)

@angersock That's a good point on the number of points. If I downsampled the yield history to monthly yields, that would probably help the performance.

Interesting that they are using kernel version 2.6.32-35. Is it common to run such an older kernel version on servers?

2.6.32 is one of the longterm maintenance releases; it's still supported and new security patches are backported. If you rent a freshly imaged RHEL/CentOS server today, that's the kernel you'll be getting. Pretty much all the software packages those distro's come with are older, longterm/stable releases, never bleeding edge.