Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #18164

A

A few more amps

Personal blog · afewmoreamps.com · on HN as aweisbergprogrammingsystems

A few more amps is a personal blog at afewmoreamps.com about programming and systems. Since 2012, 4 different Hacker News readers have linked it 4 times. The last post was in 2014, but the archive is still widely read.

Visit the blog
4mentions?
4HN people?
2012–2015first – last linked?
Links on Hacker News per year · peak 2 in 2012

Too few sampled comments (1) to say how often HN recommends it.?

Why HN links it

A personal blog whose linked post covers configuring NTP for time sync. HN readers cite it for a tip on getting sub-millisecond clock sync, in a thread about VoltDB throughput.

Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Personal log of my day to day work on Cassandra , and past work on VoltDB .

The author on HN?

aweisberg · 15 karma · member since 2010

VoltDB developer I blog about my work at http://afewmoreamps.com

From their public HN profile, which links to this site.

Most-linked posts?

  1. /2011/07/configuring-ntp-for-voltdb.html
    2 people · 2 mentions · first linked 2012-04-17

What Hacker News says?

  1. Indeed, I didn't look at latency. For time sync, I got sub-millisec syncs after using Ariel's tip at http://www.afewmoreamps.com/2011/07/configuring-ntp-for-volt... . Essentially, switching NTP off and manually running ntpdate -p 8 <server name> repeatedly can give you that. Just do it ten times in a row - I don't know why the normal operation of NTP doesn't achieve the same. This tight sync seemed to increase throu…

    Comment linking /2011/07/configuring-ntp-for-voltdb.html

    on “695k TPS with Node.js and VoltDB”
  2. Submitted A practical introduction to JMH, optimizing Selector.wakeup() as a story · 10 points

    HN discussion
  3. The intent of the test was to measure throughput. Since the API is asynchronous that means the client was submitting as much work as would fit in the queues at both client and server and any latency measurement would be a measurement of how long it takes to execute all queued requests in the pipeline and the pipeline is always kept full. I am able to get sub-millisecond offsets (as reported by ntpq -p) with m1.large…

    Comment linking /2011/07/configuring-ntp-for-voltdb.html

    on “695k TPS with Node.js and VoltDB”
  4. Submitted VoltDB, native memory, and you as a story · 2 points

    HN discussion

Search all of HN for afewmoreamps.com