zhjwpku commented on PR #13:
URL: https://github.com/apache/iceberg-cpp/pull/13#issuecomment-2545327922

   > Thanks @zhjwpku !
   > 
   > What I would be interested to know is the compile and link times, 
respectively, for both GTest and Catch2. My experience in Arrow is that GTest's 
main header `gtest.h` imposes a large compilation overhead when you have many 
independent test modules, and I'm curious if Catch2 improves the situation.
   
   I did 3 tests:
   
   1. using -E to see the preprocessed file size
      - 4301941   -- gtest
      - 4086315  -- catch2
   2. using `time` to see the compile time
      - 0.40s user 0.06s system 78% cpu 0.587 total   -- gtest
      - 0.32s user 0.06s system 76% cpu 0.494 total   -- catch2
    3. using `time` to see the link time
      - 0.04s user 0.02s system 79% cpu 0.080 total   -- gtest
      - 0.09s user 0.03s system 98% cpu 0.120 total   -- catch2
   
   As the results shows, catch2 is better at preprocessed file size and compile 
time, but gtest is better when it comes to link time. I don't think the above 
tests is adequate to prove which is better than the other, since the UT in this 
PR is fairly simple.
   
   I think we should focus closely on the specific benefits that the test 
framework is expected to deliver for this project.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

Reply via email to