Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Programming Challenge: Letter frequency

blog.p-jansson.com

Post reply on HN
Print view View original

1–3 of 3 posts

Re: Programming Challenge: Letter frequency

#2

Post by limmeau »

What can we learn from this challenge?

- decide what your benchmark shall cover and what not (computation? I/O? startup time?)

- publish compiler version and compiler options

- if the benchmark involves disk i/o, start with disk cache in a defined state (full, empty)

- avoid ambiguities in the specification ("case insensitive" -- but in which encoding? Latin-1?)

Re: Programming Challenge: Letter frequency

#3

Post by peter_jansson »

limmeau wrote: post #2

What can we learn from this challenge? - decide what your benchmark shall cover and what not (computation? I/O? startup time?) - publish compiler version and compiler options - if the benchmark involves disk i/o, start with disk cache in a defined state (full, empty) - avoid ambiguities in the specification ("case insensitive" -- but in which encoding? Latin-1?)

Yes. It is always good practice to involve more than one person when defining specifications for anything.
Post reply on HN