[DOCS] Add docs pointing to daft-launcher

[raunakab]

Overview

• added a small section pointing towards daft-launcher and how to install/use it
• placed underneath the distributed-computing section
• also added a small note to the ray section pointing towards the daft-launcher docs

[codspeed-hq]

CodSpeed Performance Report

Merging #3369 will improve performances by 53.15%

_{Comparing docs/add-launcher-docs (4af1d01) with main (60ae62f)}

Summary

⚡ 2 improvements
✅ 15 untouched benchmarks

Benchmarks breakdown

	Benchmark	main	docs/add-launcher-docs	Change
⚡	test_iter_rows_first_row[100 Small Files]	388.4 ms	335.1 ms	+15.91%
⚡	test_show[100 Small Files]	23.1 ms	15.1 ms	+53.15%

[graphite-app]

Graphite Automations

"Request reviewers once CI passes" took an action on this PR • (11/20/24)

1 reviewer was added to this PR based on Andrew Gazelka's automation.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.73%. Comparing base (60ae62f) to head (4af1d01).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3369      +/-   ##
==========================================
- Coverage   77.35%   76.73%   -0.63%     
==========================================
  Files         685      685              
  Lines       83639    84764    +1125     
==========================================
+ Hits        64703    65044     +341     
- Misses      18936    19720     +784     

see 13 files with indirect coverage changes

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[github-actions]

🚀 Deployed on https://deploy-preview-3369--daft-docs-preview.netlify.app

[ccmao1130]

For MVP it looks good to me, but I think there's a better way we can incorporate Daft Launcher in the Distributed Computing page because right now (besides looking at the left menu) users have to scroll all the way to the bottom to click to the section.

Have you also thought about how/where to reference Daft Launcher on the Ray page? https://www.getdaft.io/projects/docs/en/stable/user_guide/integrations/ray.html

[raunakab]

For MVP it looks good to me, but I think there's a better way we can incorporate Daft Launcher in the Distributed Computing page because right now (besides looking at the left menu) users have to scroll all the way to the bottom to click to the section.

Have you also thought about how/where to reference Daft Launcher on the Ray page? https://www.getdaft.io/projects/docs/en/stable/user_guide/integrations/ray.html

I can add it there if needed. Just didn't know that that was something that we wanted.

[raunakab]

CodSpeed Performance Report

Merging #3369 will degrade performances by 32.94%

Comparing docs/add-launcher-docs (e5b209d) with main (3394a66)

Summary

⚡ 2 improvements ❌ 1 regressions ✅ 14 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

Benchmark main docs/add-launcher-docs Change
⚡ test_count[1 Small File] 3.8 ms 3.5 ms +10.96%
⚡ test_iter_rows_first_row[100 Small Files] 324.1 ms 279.8 ms +15.83%
❌ test_show[100 Small Files] 15.9 ms 23.7 ms -32.94%

I'm just changing some docs! Argh!

[ccmao1130]

Hmm maybe just add something like "To run Daft on a distributed Ray cluster, see Daft Launcher [link to Daft Launcher docs on Daft docs]" wherever you see fit on the Ray page (maybe either right before "Usage" section or at the bottom of the page)

[jaychia]

What's this? We should avoid any autodoc thing that isn't standardized across the project I think, to avoid spurious refactors of the code when different developers work on the code

[jaychia]

We should also add a redirect from the poweruser/distributed-computing page to distributed-computing I believe

[jaychia]

Let's avoid nesting, just make daft-launcher a section here?

[jaychia]

We can also verify your PR is doing what we want it to do here: https://deploy-preview-3369--daft-docs-preview.netlify.app/