|
Hi,
I think intermediate results are stored in spark.local.dir (/tmp by default), not in hdfs. So if you see big latency in a shuffle-heavy operation, it's probably due to the device where /tmp reside. You can run iotop on your slaves to check where the operations are occuring. Check your wait% in top, to see if you have I/O problems You can activate the consolidateFiles option if you use ext4, it helps when dealing with big intermediate results Guillaume EC2 doesn't mount SSDs automatically, so I actually reformat those as ex4, mount them and point hdfs to them. I haven't tweaked any FS options and not sure what cause the problem. I will follow Christopher's suggestion and see whether I can find any cause.-chen --
|
- The performance of group operation on SSD Chen Jin
- Re: The performance of group operation on SSD Jay
- Re: The performance of group operation on SSD Andrew Ash
- Re: The performance of group operation on ... Matei Zaharia
- Re: The performance of group operation... Matei Zaharia
- Re: The performance of group oper... Kk.gmail
- Re: The performance of group oper... Christopher Nguyen
- Re: The performance of group operation... Chen Jin
- Re: The performance of group oper... Guillaume Pitel

