Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
stjepang's profile
Stjepan Glavina
Stjepan Glavina
Stjepan Glavina
@stjepang

Tweets

Stjepan Glavina

@stjepang

async runtimes and concurrency primitives in @rustlang he/they (available for hire)

Berlin, Germany
stjepang.github.io
Joined October 2009

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Stjepan Glavina‏ @stjepang Mar 4
      • Report Tweet
      • Report NetzDG Violation

      Before we move onto simplifying async files in Rust, it's important to learn in which areas the current implementations need improvement. This might surprise you... 1/9

      2 replies 4 retweets 42 likes
      Show this thread
    2. Stjepan Glavina‏ @stjepang Mar 4
      • Report Tweet
      • Report NetzDG Violation

      Create a random 500 MB file, read its contents using std::fs::File, and then do the same with tokio::fs::File. 2/9 dd if=/dev/urandom of=bigfile bs=1M count=500pic.twitter.com/hSdJVoFtCI

      1 reply 0 retweets 7 likes
      Show this thread
    3. Stjepan Glavina‏ @stjepang Mar 4
      • Report Tweet
      • Report NetzDG Violation

      On my machine, std takes 0.238 sec and tokio takes 120 sec, meaning tokio is 500 times slower! Note that this is not some kind of obscure edge case - we're literally just reading a big file. 3/9

      1 reply 0 retweets 8 likes
      Show this thread
    4. Stjepan Glavina‏ @stjepang Mar 4
      • Report Tweet
      • Report NetzDG Violation

      So why are async files so inefficient? Well... because reasons that are too boring for this twitter thread. The more important question to ask is: How can we be comfortable using async files if they can be 500 times too slow without even realizing it? 4/9

      2 replies 0 retweets 6 likes
      Show this thread
    5. Stjepan Glavina‏ @stjepang Mar 4
      • Report Tweet
      • Report NetzDG Violation

      And performance is not the only pitfall of async files. Here's another - write some bytes into a tokio::fs::File. If you forgot to flush before dropping the file, some buffered data will be lost! In this example, the created file is empty. 5/9pic.twitter.com/PFJEsduJiB

      1 reply 0 retweets 7 likes
      Show this thread
    6. Stjepan Glavina‏ @stjepang Mar 4
      • Report Tweet
      • Report NetzDG Violation

      Perhaps most surprisingly, async-std/tokio files are *always* slower than std files. They don't improve performance at all, quite the opposite - their only utility is in that they move blocking file I/O onto a dedicated thread pool. But you can also do that yourself anyway. 6/9

      1 reply 0 retweets 6 likes
      Show this thread
    7. Stjepan Glavina‏ @stjepang Mar 4
      • Report Tweet
      • Report NetzDG Violation

      If you do want fast async files, consider using rio by @sadisticsystems instead. That is really the only way! 7/9 https://github.com/spacejam/rio  https://docs.rs/rio 

      3 replies 3 retweets 23 likes
      Show this thread
    8. Stjepan Glavina‏ @stjepang Mar 4
      • Report Tweet
      • Report NetzDG Violation

      My advice is to avoid async files in Rust altogether because they're inefficient and full of pitfalls (unless you use rio). Use them only in situations when you know what you're doing, if ever. Things might get different in the future, but that is what I advise *today*. 8/9

      2 replies 0 retweets 11 likes
      Show this thread
    9. Zeeshan  🦀 🚁 🛩️ ⚡‏ @zeenix Mar 4
      • Report Tweet
      • Report NetzDG Violation
      Replying to @stjepang

      not really a choice in UIs so rio it is!

      2 replies 0 retweets 0 likes
      Stjepan Glavina‏ @stjepang Mar 4
      • Report Tweet
      • Report NetzDG Violation
      Replying to @zeenix

      What about calling spawn_blocking() and doing synchronous file I/O there? Is that an option?

      9:01 AM - 4 Mar 2020
      • 1 Like
      • Zeeshan 🦀🚁🛩️⚡
      1 reply 0 retweets 1 like
        1. Zeeshan  🦀 🚁 🛩️ ⚡‏ @zeenix Mar 4
          • Report Tweet
          • Report NetzDG Violation
          Replying to @stjepang

          indeed it is, and didn't pay attention to that bit, sorry. Just a tiny bit more cognitive load there though. Generally, we've been telling people to always use the async IO API so a bit of unlearning/relearning involved here as well it think..

          0 replies 0 retweets 1 like
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info