Hi Clive,
This is strange. We were not aware of this performance hit.
1) Can you verify that the macro
#define GRAPHCHI_DISABLE_COMPRESSION
is defined on your latest version? This can easily explain x2 speedup.
2) There was one change in the code, that first top K results are computed, sorted and then
saved to disk. (Previously, we would save all results to disk, and later you had to sort
and find the top K). This change consumes more memory but maybe slows down the run.
3) --nshards=1 should increase performance since it forces the full graph to be loaded into memory
and thus saves a lot of disk reads.
Best,