Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-136896905
@zsxwing is this outdated now that we have pagination?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user zsxwing closed the pull request at:
https://github.com/apache/spark/pull/7071
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-136897781
> @zsxwing is this outdated now that we have pagination?
Yes. I think we don't need it. Closing it.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-121071365
Merged build triggered.
---
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
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-116596423
I have never seen the situation you mentioned even when there are 1
tasks. The contents below the timeline are rendered immediately with my browser
(Chrome,
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-116609232
I wonder this issue may depend on environments.
I think it depends on the performance of CPU. My CPU is 2.7G i7.
`drawTaskAssignmentTimeline` is not very fast
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-116484699
@zsxwing Did you profile after patching? I spent some times to profile
before-patching and after-patching 2 times for each, with 1 tasks. I
couldn't recognized
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-116485150
This PR is not for rendering speedup. It's just for people to be able to
view the page before finishing rendering the timeline.
---
If your project is set up for it,
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-116484869
For more information, I've tested using Chrome 39.0.2171.71.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-116509232
And as I mentioned above, I was made to wait to view timeline until
entire page is rendered.
Sorry that it's not clear about the purpose of this PR.
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-116499706
As you can see the captures, the time I wait until I can view the page was
not so different between before patching and after.
And as I mentioned above, I was made
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-116437163
Updated it.
---
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
12 matches
Mail list logo
