News for hackers. Stuff that matters.

gophernaught

Re:Prometheus reaches 1.0 on Monday July 18, 2016 @08:00PM (#12118695)
Metrics are pretty cheap, unless you have a ton of exporters I wouldn't worry too much about that. Plus it can come in handy: the ZFS exporter I wrote uses a CGO library that had a memory leak, which I discovered thanks to those app metrics. And they made it easy to infer that the leak was in the C heap rather than in Go.
Re:Prometheus reaches 1.0 on Monday July 18, 2016 @02:22PM (#12117054)
Funny coincidence, yesterday I did almost the same thing, though mine's based on lm-sensors and hddtemp:

https://github.com/ncabatoff/sensor-exporter

Re:Prometheus reaches 1.0 on Monday July 18, 2016 @12:26PM (#12116064)
Hooray! Couldn't come at a better time for me, we're about to roll it out to all our customers and the API stability promises are great news.

Many thanks to the authors for all their hard work, and congrats.

Re:Show HN: Concurrency-safe file-backed element store in Go on Saturday February 28, 2015 @11:30AM (#9124111)
Whoops, by os.Sync() I meant *File.Sync() of course, aka fsync.
Re:Show HN: Concurrency-safe file-backed element store in Go on Saturday February 28, 2015 @11:09AM (#9124032)
I like it, though I think it's likely to create a lot of garbage, what with spawning a goroutine on each Put, I suppose that's probably not an issue for most programs.

I find defer pretty expensive, I don't use them that liberally anymore, only when they're really called for.

Bug: defer fh.Close() without error checking in put(). This can result in data loss. It would also be nice to at least have the option of doing synchronous stores, possibly even with an os.Sync().