The Billion Rows Challenge in Rust - an intro to Rust for data engineering

Поділитися
Вставка
  • Опубліковано 12 січ 2025

КОМЕНТАРІ • 26

  • @rahuldevstech
    @rahuldevstech 10 місяців тому +15

    "On the planet to build a better planet"! As a Python data engineer with a background in environmental sciences, that resonates a lot with me. Thank you for what you do!

    • @mrlectus
      @mrlectus 10 місяців тому

      python doesn't help with the environment

    • @rahuldevstech
      @rahuldevstech 10 місяців тому +5

      ​​@@mrlectus Agreed. Trying to change the tech stack where I'm at to use Rust 🦀 Needless to say, Tim's content helps me a lot with that!

  • @theuberlord7402
    @theuberlord7402 10 місяців тому +3

    Nice to see a Kiwi leading the charge on Rust education and advocacy.

  • @flwi
    @flwi 10 місяців тому

    Thanks for taking the time to explain your workflow in such great detail! Glad I found your channel just now, because I started learning rust this weekend

  • @coolbuddy95able
    @coolbuddy95able 10 місяців тому +1

    Great video! Couple of weeks ago I picked up Rust, and I'm loving it. Would have been good if you could benchmark it in the video. Any chance you did it offline?

  • @omaslo
    @omaslo 10 місяців тому

    Thank you for this stream! So many interesting things explained!

  • @sergeykuznetsov7688
    @sergeykuznetsov7688 9 місяців тому

    Thanks for the video! While watching I wanted to experiment with so many things so I ended up solving it by myself for both single and multi thread modes. Being quite simple It turns out to be a very educative problem.

    • @timClicks
      @timClicks  9 місяців тому

      Nice work! I'm so glad that you have fun playing around.

  • @knolljo
    @knolljo 10 місяців тому

    Love the challenge, thanks!

  • @sidkang
    @sidkang 10 місяців тому

    wow, really interesting topic, happy to see this. Thanks!

  • @andydataguy
    @andydataguy 10 місяців тому

    Ooo can't wait to watch this!

  • @learning_rust
    @learning_rust 10 місяців тому

    I'm just curious - if f32 would have been sufficient for the temperature, and if so, would that make any performance improvement?
    I come from Python background so naive on this and keen to learn!

    • @julians.2597
      @julians.2597 8 місяців тому +2

      Measure, measure, measure. Only way to show performance differences, and then only on specific setups

    • @SPeeSimon
      @SPeeSimon 5 місяців тому +1

      Look at the java examples and what they did there. The fastest ones are working with the raw bytes and not converting it into a string, f32 or f64 type.
      It would be great to see if a rust example can achieve the same kind of high speeds. Is it still easy to write and read if you are using multithreaded and direct file reading? Or is that not something a good dev can create as compared to java.

  • @michaelwagner4801
    @michaelwagner4801 8 місяців тому +2

    The accent character is called an umlaut

  • @GlobalYoung7
    @GlobalYoung7 10 місяців тому

    thank you😀

  • @minciNashu
    @minciNashu 10 місяців тому +2

    else isn't mandatory after if-let.

  • @hanling8489
    @hanling8489 9 місяців тому +1

    like it

  • @JOHNSMITH-ve3rq
    @JOHNSMITH-ve3rq 10 місяців тому

    Brother is Aussie?? Cool!

    • @timClicks
      @timClicks  10 місяців тому

      New Zealander, but close enough 😂

  • @dim-2d
    @dim-2d 6 місяців тому

    Didn’t finish the whole video yet, but you’re supposed to store the MEAN not the average…
    Edit: My bad, I read "mean" and my brain understood it as "median". Sorry about that.

    • @Gramini
      @Gramini 5 місяців тому

      What's the difference? From what I gathered they're pretty much identical. It seemed to me that they differ in some technical math terms regarding their history, but that's not not really important in the broader sense.
      "the mean is the average of all the data values"

    • @dim-2d
      @dim-2d 5 місяців тому +1

      @@Gramini I'm sorry, you're absolutely right. For whatever reason I read "mean" and I understood it as "median". A median (which in this case it is NOT, my bad) would change the implementation quite significantly.