Github user JoshRosen commented on a diff in the pull request:

    https://github.com/apache/spark/pull/2351#discussion_r17993579
  
    --- Diff: docs/configuration.md ---
    @@ -207,6 +207,22 @@ Apart from these, the following properties are also 
available, and may be useful
       </td>
     </tr>
     <tr>
    +  <td><code>spark.python.profile</code></td>
    +  <td>false</td>
    +  <td>
    +    Enable profiling in Python worker, the profile result will show up by 
`rdd.show_profile()`,
    +    or it will show up before the driver exit. It also can be dumped into 
disk by
    +    `rdd.dump_profile(path)`.
    +  </td>
    +</tr>
    +<tr>
    +  <td><code>spark.python.profile.dump</code></td>
    +  <td>(none)</td>
    +  <td>
    +    The directory which is used to dump the profile result. The results 
will be dumped
    +    as sepereted file for each RDD. They can be loaded by ptats.Stats().
    --- End diff --
    
    Typo: "sepereted" -> "a separate".
    
    It looks like this `spark.python.profile.dump` is only used for dumping 
files when the job exits?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to