Thank you very much for the figures.
I can understand why tdbloader is affected by the change in RAM size.
But your (and mime, recently) experience with tdbloader2 is mysterious
to me currently.
Andy
On 05/11/13 06:06, Neubert Joachim wrote:
I repeated the data loading with 32 G
I repeated the data loading with 32 G mem (instead of 11 G, see below).
tdbloader2 showed a slight improvement:
tdbloader2
0:30 Data phase
5:45 Index phase
Almost all of index phase (which seems to have taken longer with more memory -
could have been caused by parallel activities on the vm
