Github user caneGuy commented on the issue:

    https://github.com/apache/spark/pull/18730
  
    Update with 
[Benchmark](https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/util/Benchmark.scala)
 @kiszk 
    ```
    Running benchmark: Benchmark writeWithSlice() and writeFully()
      Running case: Test writeFully() chunks each with 30m for 10 loop
      Stopped after 10 iterations, 2365 ms
      Running case: Test writeWithSlice() chunks each with 30m for 10 loop
      Stopped after 10 iterations, 1440 ms
      Running case: Test writeFully() chunks each with 100m for 50 loop
      Stopped after 50 iterations, 2860 ms
      Running case: Test writeWithSlice() chunks each with 100m for 50 loop
      Stopped after 50 iterations, 2834 ms
    
    Java HotSpot(TM) 64-Bit Server VM 1.8.0_25-b17 on Linux 4.4.0-64-generic
    Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
    Benchmark writeWithSlice() and writeFully(): Best/Avg Time(ms)    Rate(M/s) 
  Per Row(ns)   Relative
    
------------------------------------------------------------------------------------------------
    Test writeFully() chunks each with 30m for 10 loop        98 /  237        
160.8           6.2       1.0X
    Test writeWithSlice() chunks each with 30m for 10 loop        55 /  144     
   287.6           3.5       1.8X
    Test writeFully() chunks each with 100m for 50 loop        54 /   57        
290.3           3.4       1.8X
    Test writeWithSlice() chunks each with 100m for 50 loop        54 /   57    
    288.9           3.5       1.8X
    ```


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to