Comments on: Measuring Startup

By: vladimir

vladimir — Wed, 29 Jul 2009 17:29:33 +0000

Yeah, could’ve used perl as well; python is a standard part of our build system install though, and so is generally more available. The startup time of python is irrelevant; only the time from print until the process exits. Doing “python … ; datemsec” (where datemsec was my standalone C program), the number from datemsec was generally only 1-2 msec more.

I would’ve liked to use date, but %N is a nonstandard GNU extension.

By: Scott Baker

Scott Baker — Wed, 29 Jul 2009 15:09:22 +0000

You can use unix date also. It might be a little faster than loading all of python just to spit out unix epoch seconds.

date %s.%N

By: Ernst Persson

Ernst Persson — Wed, 29 Jul 2009 11:18:58 +0000

I was thrilled when I found clock_gettime in libc, it’s perfect for benchmarking (on linux anyway). You have both CLOCK_REALTIME and CLOCK_PROCESS_CPUTIME_ID for example.

By: Simon Proctor

Simon Proctor — Wed, 29 Jul 2009 08:14:10 +0000

I saw that python one liner and my first thought was:

perl -e ‘print time’

But I’ve spent way too much time writing perl.

By: adw

adw — Wed, 29 Jul 2009 04:13:52 +0000

These startup posts are great, but you really buried the lede with that Armstrong and Miller video.