I thought, I had broken the iteration-time foldout of ReBenchDB. Turns out, it was just terribly slow.
Scanning through a 2GB data table on a slow disk takes a while.
Fix the primary key order, i.e., the relevant index, and instead of waiting 42sec, it shows in 34ms.
