strange benchmark logs. where is the command used for creating reiser4?
if during creation the flavour cryptcompress was chosen, maybe even with always-compress, it's an unfair comparison. this would explain why it performs so poorly in multithreading: all processors (especially on intel the "cores") are occupied with number-crunching for the compression.
or did the other filesystems have some compression feature turned on too? on ssd compression might be a bad idea anyway...