commit stats for fflf-ispn53 using 0mq (not the best ones)

These results were taken still:

  - with the 'inTransaction' bug in radargun
  - without indexing the read set
  - using writePercentage and a percentage and not as an absolute number of
    writes
FutureGrid results. The latest are quite good.

Results in
auto-results.20131121-114900-FF@8246873-RG@56a4b01-indexingReadset-writeset1-withCommitStats
use:

  - print commit stats
  - indexed read set for intersections
  - write set size = 1
  - radargun bug with 'inTransaction' fixed.

Supposedly the last item accounts for the reduction in performance in
RW10-100-1p and RW20-100-1p when compared to previous runs.  I re-run the
tests without the first two items and the results were the same.  The only
delta was thus on the write set size and the 'inTransaction' fix.  While the
write set size could affect the results (higher rate of transactions?), and
fairly confident that the bug fix is the explanation.
More FutureGrid results. Now with ispn53 and fflf-ispn53 --- not as good :-(
update scripts that process future grid results
deimos: RW{01,05,10,20} for {100,1000,10000} 1p using 0mq (WITH AFFINITY and HWM=0) (should go to thesis)
FutureGrid: RW{01,05,10,20} for {100,1000,10000} 1p using 0mq (WITH AFFINITY and HWM=0) (EHCACHE and FF-LF) (should go to thesis)