for this
behavior?
Best regards,
Simon
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/KMeans-for-large-training-data-tp9407p9508.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
-list.1001560.n3.nabble.com/KMeans-for-large-training-data-tp9407p9509.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
code (where it gets slow) is this:
What could I do to use more executors, and generally speed this up?
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/KMeans-for-large-training-data-tp9407.html
Sent from the Apache Spark User List mailing list archive
it
wrong. The relevant code (where it gets slow) is this:
What could I do to use more executors, and generally speed this up?
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/KMeans-for-large-training-data-tp9407.html
Sent from the Apache Spark User
On Fri, Jul 11, 2014 at 7:32 PM, durin m...@simon-schaefer.net wrote:
How would you get more partitions?
You can specify this as the second arg to methods that read your data
originally, like:
sc.textFile(..., 20)
I ran broadcastVector.value.repartition(5), but