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
burntsushi5's profile
Andrew Gallant
Andrew Gallant
Andrew Gallant
@burntsushi5

Tweets

Andrew Gallant

@burntsushi5

I love to code.

Marlborough, MA
blog.burntsushi.net
Joined October 2016

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. Andrew Gallant‏ @burntsushi5 7 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @burntsushi5 @boyter

      Also, note that a good chunk of that is probably going to be benchmarking output, which probably defeats some of the purpose of the comparison. If you do `rg '^.+$' -c`, which will count every match instead of printing every match, then you might get a bit closer.

      2 replies 0 retweets 1 like
    2. boyter‏ @boyter 7 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @burntsushi5

      To be honest I was using ripgrep to A warm up the disk cache and B just give a reasonable idea of how fast its possible to move through the code. Noticed your comments on https://www.reddit.com/r/rust/comments/82k9iy/loc_count_lines_of_code_quickly/ … which is what I am now benching against :)

      1 reply 0 retweets 0 likes
    3. Andrew Gallant‏ @burntsushi5 7 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @boyter

      Great! Sounds like you're on the right track. :-)

      1 reply 0 retweets 0 likes
    4. boyter‏ @boyter 7 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @burntsushi5

      Hope so! Never needed to write code with this level of performance requirements before. Rather refreshing way to think about things.

      1 reply 0 retweets 1 like
    5. Andrew Gallant‏ @burntsushi5 11 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @boyter

      w.r.t. https://github.com/boyter/scc  I really think you should be giving the `-c` flag to ripgrep. Line counters print aggregate statistics, and comparing that with a command that prints virtually every line that it prints it not particularly meaningful. :-)

      1 reply 0 retweets 1 like
    6. boyter‏ @boyter 11 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @burntsushi5

      Its funny, I tried that and it made no real difference. Not sure what voodoo hyperfine is doing under the hood. Ill add it in when I do the real benchmarks though. Still a long way to go before that happens though :)

      1 reply 0 retweets 1 like
    7. Andrew Gallant‏ @burntsushi5 11 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @boyter

      Strange. It made a *dramatic* difference on my end (using hyperfine). I also can't seem to reproduce your relative ranking on the single threaded benchmarks, but it's not too different.

      2 replies 0 retweets 1 like
    8. boyter‏ @boyter 11 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @burntsushi5

      I hate benchmarks :) Keep in mind most of mine are taken on WSL which is probably dramatically affecting the results. I will just remove the current ones from the http://README.md  till I do the real results.

      1 reply 0 retweets 1 like
    9. Andrew Gallant‏ @burntsushi5 11 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @boyter

      Oooo. I forgot about WSL. Yeah, perf characteristics can be completely different on Windows. I only recently discovered that Windows Defender plays a very large role in the performance of ripgrep for example.

      1 reply 0 retweets 1 like
    10. boyter‏ @boyter 11 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @burntsushi5

      Yep it does for everything in the WSL. Way different performance characteristics. I should spin up a VM for trialing closer to native. When I do real benchmarks I will use a few AWS instances.

      1 reply 0 retweets 0 likes
      Andrew Gallant‏ @burntsushi5 11 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @boyter

      Be careful with VMs too. I found that they penalized memory maps quite a bit!

      8:19 PM - 11 Mar 2018
      • 1 Like
      • boyter
      1 reply 0 retweets 1 like
        1. boyter‏ @boyter 11 Mar 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @burntsushi5

          Yep. Can't win either way really. Ill just aim for the best performance I can and then worry later. So long as others can repeat the benchmarks and get similar results it should be fine... I hope!

          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