Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r97211797
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -602,6 +619,20 @@ class
Github user witgo commented on the issue:
https://github.com/apache/spark/pull/15505
@squito
My understanding is that the TaskSchedulerImpl class contains many
synchronized statements (synchronized the methods). If a synchronized
statements execution time is very long, it will
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r97695455
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -602,6 +619,21 @@ class
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r99457658
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -243,27 +245,42 @@ class
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r99458022
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskDescription.scala ---
@@ -66,7 +100,8 @@ private[spark] object TaskDescription
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r99458165
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskDescription.scala ---
@@ -51,8 +54,39 @@ private[spark] class TaskDescription(
val index
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r99458252
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskDescription.scala ---
@@ -51,8 +54,39 @@ private[spark] class TaskDescription(
val index
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r99462387
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -243,27 +245,42 @@ class
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r99462431
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskDescription.scala ---
@@ -66,7 +100,8 @@ private[spark] object TaskDescription
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r99462808
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -243,27 +245,42 @@ class
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r99463382
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -244,32 +245,45 @@ class
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/16806
[WIP][SPARK-18890][CORE] Move task serialization from the TaskSetManager to
the CoarseGrainedSchedulerBackend
## What changes were proposed in this pull request?
See https
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/16806
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r99848516
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -243,27 +245,42 @@ class
Github user witgo commented on the issue:
https://github.com/apache/spark/pull/15505
Okay, this may take some time.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r93558401
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -136,14 +136,10 @@ private[spark] class Executor(
startDriverHeartbeater
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r93558431
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -232,6 +225,13 @@ private[spark] class Executor
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r93558450
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -993,6 +993,12 @@ class DAGScheduler
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r93558472
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskDescription.scala ---
@@ -17,27 +17,179 @@
package org.apache.spark.scheduler
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r93558527
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskDescription.scala ---
@@ -17,27 +17,179 @@
package org.apache.spark.scheduler
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r93558564
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/local/LocalSchedulerBackend.scala
---
@@ -59,6 +62,12 @@ private[spark] class LocalEndpoint
Github user witgo commented on the issue:
https://github.com/apache/spark/pull/14658
Spark 2.2 has fixed this issue.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/21451#discussion_r191628993
--- Diff:
common/network-common/src/main/java/org/apache/spark/network/server/RpcHandler.java
---
@@ -38,15 +38,24 @@
*
* This method will
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/21451#discussion_r192279111
--- Diff:
common/network-common/src/main/java/org/apache/spark/network/server/RpcHandler.java
---
@@ -38,15 +38,24 @@
*
* This method will
Github user witgo commented on the issue:
https://github.com/apache/spark/pull/14995
I did not do much testing, but I think it can be used in the production
environment
the url:
https://github.com/witgo/spark/tree/SPARK-6235_Address_various_2G_limits
---
If your project is set
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/21346#discussion_r195284967
--- Diff:
common/network-common/src/main/java/org/apache/spark/network/client/TransportClient.java
---
@@ -220,30 +196,91 @@ public long sendRpc(ByteBuffer
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/21346#discussion_r195287202
--- Diff:
common/network-common/src/main/java/org/apache/spark/network/protocol/UploadStream.java
---
@@ -0,0 +1,107 @@
+/*
+ * Licensed to the
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/5456
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/5548
[SPARK-6963][CORE]Flaky test: o.a.s.ContextCleanerSuite automatically
cleanup checkpoint
cc @andrewor14
You can merge this pull request into a Git repository by running:
$ git pull https
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/5548#discussion_r28581367
--- Diff: core/src/test/scala/org/apache/spark/ContextCleanerSuite.scala ---
@@ -245,7 +245,7 @@ class ContextCleanerSuite extends
ContextCleanerSuiteBase
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/5548#discussion_r28583156
--- Diff: core/src/test/scala/org/apache/spark/ContextCleanerSuite.scala ---
@@ -245,7 +245,7 @@ class ContextCleanerSuite extends
ContextCleanerSuiteBase
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/5548#discussion_r28584757
--- Diff: core/src/test/scala/org/apache/spark/ContextCleanerSuite.scala ---
@@ -427,12 +429,17 @@ class CleanerTester(
def broadcastCleaned
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/5591#discussion_r28685371
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/regression/FactorizationMachine.scala
---
@@ -0,0 +1,539 @@
+package
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/5591#discussion_r28685417
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/regression/FactorizationMachineSuite.scala
---
@@ -0,0 +1,245 @@
+package
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-95117217
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/5716
[SPARK-7162][YARN]Launcher error in yarn-client
jira: https://issues.apache.org/jira/browse/SPARK-7162
You can merge this pull request into a Git repository by running:
$ git pull https
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/5716#issuecomment-96550921
cc @vanzin
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/3867
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/3989
[Minor]Resolve sbt warnings during build (MQTTStreamSuite.scala).
cc @andrewor14
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/4047#issuecomment-70030602
There are two questions.
1. How to cover the long tail topic features
2. The algorithm performance in 10K -100K topic
Here is a relevant
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/1387
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/3051
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/3222#issuecomment-70984655
witgo#qq.com
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/4263
[SPARK-5474][Build]curl should support URL redirection in build/mvn
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-5474
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/4263#issuecomment-72040666
I test in Max OS x and centos 6.4 system, there is no problem.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-72069846
Here is a sample faster branch(work in progress):
https://github.com/witgo/spark/tree/lda_MH
---
If your project is set up for it, you can reply to this email and
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/4263#issuecomment-72165108
@pwendell It seems that only this URL(download maven) might return 3xx.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2379#issuecomment-56810769
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/2379#discussion_r18070980
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -1357,6 +1357,58 @@ private[spark] object Utils extends Logging
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2311#issuecomment-56912003
Ok, no problem.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2311#issuecomment-56914209
Yes, this does not involve `org.apache.spark.deploy.yarn.Client` class,
which run outside the cluster.
We should call `YarnClient.killApplication` when an uncaught
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/1983
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/2379#discussion_r18121155
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -1357,6 +1357,58 @@ private[spark] object Utils extends Logging
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/2379#discussion_r18121404
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -1357,6 +1357,58 @@ private[spark] object Utils extends Logging
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2379#issuecomment-57040105
@andrewor14 The code has been updated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/2376
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2376#issuecomment-57078975
I temporarily can not reproduce it, and close this PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/2524#discussion_r18128796
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -112,6 +112,10 @@ class DAGScheduler(
// stray messages to
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-57199913
The current solution is simple to implement.If we don't do so,we have to
change a lot of existing code.
---
If your project is set up for it, you can reply to this
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/2577#discussion_r18170801
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -450,6 +539,15 @@ object ApplicationMaster extends Logging
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/2311
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-57572266
Ok, I'll try to use LD_LIBRARY_PATH.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/2631
[WIP][SPARK-3625][SPARK-3623]Graph should support the checkpoint operation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-3623
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2379#issuecomment-58305582
@andrewor14 The code has been updated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/2711
[WIP][SPARK-1720][SPARK-1719] use LD_LIBRARY_PATH instead of
-Djava.library.path
This is another implementation about #1031
You can merge this pull request into a Git repository by running
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/2730
[Minor] use norm operator after breeze 0.10 upgrade
cc @mengxr
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-3856
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2711#issuecomment-58530530
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/2711#discussion_r18686842
--- Diff:
core/src/main/scala/org/apache/spark/deploy/worker/CommandUtils.scala ---
@@ -38,6 +40,20 @@ object CommandUtils extends Logging
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2752#issuecomment-58655305
This will cause some bug.
It seems to be related to `akka.remote.retry-gate-closed-for` configuration
the log:
```
14/10/10 20:56:03 WARN
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/2388
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-58680646
Found a bug, and I'm trying to figure out what the problem.
I close this temporarily.
---
If your project is set up for it, you can reply to this email and have
GitHub user witgo reopened a pull request:
https://github.com/apache/spark/pull/2388
[WIP][SPARK-1405][MLLIB] topic modeling on Graphx
This PR relies on #2631
- [X] Topic de-duplication
- [X] Support 10 topics
- [X] Asymmetric Dirichlet priors
- [ ] Add
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/2763
The keys for sorting the columns of Executor page ,Stage page Storage page
are incorrect
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/2388#discussion_r18740868
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/TopicModeling.scala ---
@@ -0,0 +1,674 @@
+/*
+ * Licensed to the Apache Software
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/2388#discussion_r18768316
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/TopicModeling.scala ---
@@ -0,0 +1,682 @@
+/*
+ * Licensed to the Apache Software
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/1754
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2786#issuecomment-58986316
Cool, this is a very good improvement.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2784#issuecomment-58989319
This configuration seems to be the value in milliseconds.
https://github.com/akka/akka/blob/v2.3.4/akka-remote/src/main/scala/akka/remote/DeadlineFailureDetector.scala
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2784#issuecomment-58989797
Sorry, I made a mistake.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2379#issuecomment-59153778
@andrewor14 The code has been updated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2379#issuecomment-59159165
Cool! Thanks @andrewor14 @vanzin
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/2846
[SPARK-3997][Build]scalastyle should output the error location
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-3997
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/855#issuecomment-76114183
@andrewor14 @tdas The code has been updated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/3744#issuecomment-76126729
Two months ago. I talked to @mengxr in an email, I will post the
performance test results
---
If your project is set up for it, you can reply to this email and have your
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/3744#issuecomment-76143785
```scala
test("bernoulli sampling benchmark") {
class BernoulliSamplerBenchmark(val fraction: Double, items: () =>
Iterator[
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/4908
Resolve sbt warnings: postfix operator second should be enabled
Resolve sbt warnings:
```
[warn]
spark/streaming/src/main/scala/org/apache/spark/streaming/util
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/4908#issuecomment-77376561
Yes.
This patch only resolves the postfix build warnings.
I can try to resolve more build warnings, we should create a JIRA.
---
If your project is set up for it
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/4908#issuecomment-77556717
@srowen
You can merge this PR. Other changes I will create a new JIRA and PR.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/4807#issuecomment-78089533
@EntilZha @mengxr This branch can be merged into master?
I want merge the PR to
[LightLDA](https://github.com/witgo/spark/tree/LightLDA) and
[lda_Gibbs](https
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/4807#issuecomment-78189159
@EntilZha thx.
@mengxr what do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/4807#discussion_r26186996
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/clustering/LDA.scala
---
@@ -311,165 +319,319 @@ private[clustering] object LDA {
private
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/4807#discussion_r26187041
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/clustering/LDA.scala
---
@@ -311,165 +319,319 @@ private[clustering] object LDA {
private
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/4807#discussion_r26188379
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/clustering/LDA.scala
---
@@ -311,165 +319,319 @@ private[clustering] object LDA {
private
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/4807#discussion_r26188380
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/clustering/LDA.scala
---
@@ -311,165 +319,319 @@ private[clustering] object LDA {
private
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/4807#discussion_r26189615
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/clustering/LDA.scala
---
@@ -311,165 +319,319 @@ private[clustering] object LDA {
private
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/4807#issuecomment-78486179
@jkbradley, @mengxrWhether have time to look at here?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-82685857
The MLLIB existing infrastructure(BSP) is not suitable for large scale
distributed neural net
There are JIRA about the parameters server.
[SPARK-4590](https
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-82750982
Parameter server + matrix calculations is usually more common.
The performance of matrix calculations is better.
---
If your project is set up for it, you can reply
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-82767499
This seems to be worth a try. @avulanov what do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/3222
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
401 - 500 of 916 matches
Mail list logo
