Redis 8.0-M3 Brings Async I/O Threading, 12x Speed-Up With New AVX2 Code Path

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • phoronix
    Administrator
    • Jan 2007
    • 67328

    Redis 8.0-M3 Brings Async I/O Threading, 12x Speed-Up With New AVX2 Code Path

    Phoronix: Redis 8.0-M3 Brings Async I/O Threading, 12x Speed-Up With New AVX2 Code Path

    For those making use of the source-available Redis in-memory key-value database, the upcoming Redis 8.0 will offer better performance on today's high core count systems and servers...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
  • Kjell
    Senior Member
    • Apr 2019
    • 683

    #2
    Redis is dead

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

    Comment

    • Kjell
      Senior Member
      • Apr 2019
      • 683

      #3
      I deeply despise companies which profit off open-source contributions just to pull the rug once the product becomes popular

      VyOS is the latest example
      Last edited by Kjell; 23 January 2025, 01:35 PM.

      Comment

      • peterdk
        Senior Member
        • Feb 2020
        • 203

        #4
        Originally posted by Kjell View Post
        I deeply despise companies which profit off open-source contributions just to pull the rug once the product becomes popular

        VyOS is the latest example
        I did a bit of googling, but can't find anything about VyOS license issues. Have a link?

        Comment

        • CommunityMember
          Senior Member
          • Oct 2019
          • 1375

          #5
          Originally posted by Kjell View Post
          Redis is dead
          While the company may have seriously injured itself in regards to the community, it is not dead, at least not as of today.

          While the hyperscalers have/are moving to Valkey (including, importantly, their engineering efforts), there are still organizations who will continue to run redis, at least for the time being, as there is no (to them) advantage to invest in the migration and QA that such a move entails (in industries which requires validation and certification you can't just swap out software).

          It will be interesting to see what the next round of funding values the company at.

          Comment

          • Guiorgy
            Phoronix Member
            • Jul 2024
            • 51

            #6
            Originally posted by Kjell View Post
            I deeply despise companies which profit off open-source contributions just to pull the rug once the product becomes popular

            VyOS is the latest example
            And yet the ccompanies that see open source as free suppliers that should be happy to work for them for free are totally fine? With that said, I too hate how their move felt like a rugpull to the whole community. I wonder if them abandoning the Reddis project (and name) and making a fork with their current license would've been any better in the eyes of the community?

            Comment

            • Kjell
              Senior Member
              • Apr 2019
              • 683

              #7
              Originally posted by peterdk View Post
              I did a bit of googling, but can't find anything about VyOS license issues. Have a link?
              When Vyatta became closed source it got forked into VyOS. They stated they'd never "Make a proprietary or freemium versions of VyOS"

              freemium
              /ˈfriːmɪəm/
              noun
              a business model, especially on the internet, whereby basic services are provided free of charge while more advanced features must be paid for.


              Down the road this turned out to not be the case. VyOS started shipping closed source VPP module and they were annoyed by homelab users for asking if it would be open source

              Hi everyone, I’ve been following the latest development updates over the last few months and I’ve been interested in the VPP Addon for some future plans in my home lab. It’s clear to me that is still under development and experimental. However, what I would like to understand is if the VPP Addon will also be Open Source eventually, or behind a paywall? Thank you.


              VyOS later spiraled into removing source code for their stable releases as well as all endpoints serving the required build files while restricting access to business users through very expensive license

              Patches for multiple CVEs, Base64-encoded IPsec secrets, and multiple bug fixes — read on for details! #vyos #release #1.4.1 #networking #updates


              This left its community with no way to acquire any builds of VyOS for months while keeping the community in the dark.

              After a lot outrage they just released "VyOS Stream" which serves developments builds of their software and project's development source code remains mostly open

              Their recent actions leave bad faith in the project considering VyOS is built on open source projects and community contributions.
              Last edited by Kjell; 23 January 2025, 05:01 PM.

              Comment

              • CommunityMember
                Senior Member
                • Oct 2019
                • 1375

                #8
                Originally posted by Kjell View Post
                Down the road this turned out to not be the case. VyOS started shipping closed source VPP module
                Adding proprietary extensions on top of open source software and charging for it, or charging for support, is not exactly a new thing. As I understand it, VPP is (was?) primarily just DPDK in VyOS clothing.

                I have not closely followed the current state of VyOS, but as I recall they offered a free license to the LTS & VPP functionality to contributors.

                I am not sure what level of contribution they consider to be substantial. Are you saying you contribute and can't get a license?

                Of course, the community would seem to be free to develop their own DPDK module. Somewhat wasted duplicated effort, but then we have many examples of duplicated effort (with slight tweaks) in the Linux ecosystem, so nothing new there, either.

                Comment

                • Kjell
                  Senior Member
                  • Apr 2019
                  • 683

                  #9
                  Originally posted by CommunityMember View Post

                  Adding proprietary extensions on top of open source software and charging for it, or charging for support, is not exactly a new thing. As I understand it, VPP is (was?) primarily just DPDK in VyOS clothing.

                  I have not closely followed the current state of VyOS, but as I recall they offered a free license to the LTS & VPP functionality to contributors.

                  I am not sure what level of contribution they consider to be substantial. Are you saying you contribute and can't get a license?

                  Of course, the community would seem to be free to develop their own DPDK module. Somewhat wasted duplicated effort, but then we have many examples of duplicated effort (with slight tweaks) in the Linux ecosystem, so nothing new there, either.
                  Understandable, but VPP is included in FOSS FRRouting that VyOS uses which makes this even stranger

                  Furthermore donating was a way to acquire a license for hobby users/homelab but that got removed which makes sense if VyOS' goal is Enterprise

                  Ultimately the state of VyOS is very ingenuine due to lack of transparency with devs often ignoring such questions and leaving users hanging

                  I'm all for the project making money but the fact that VyOS is a glorified configuration engine that benefits off open source work leaves a bad taste, one example being containers in their documentation

                  Their act isn't aligning with their original notion of being community oriented. Every time I've seen this in the past in other projects it all ends the same way
                  Last edited by Kjell; 24 January 2025, 08:26 AM.

                  Comment

                  • NotMine999
                    Senior Member
                    • Feb 2014
                    • 1032

                    #10
                    Originally posted by Kjell View Post

                    When Vyatta became closed source it got forked into VyOS. They stated they'd never "Make a proprietary or freemium versions of VyOS"

                    {removed excrutiatingly long user-written article}
                    The poster asked of a link and you wrote a bloody article.

                    Lucky the poster did not ask for a book or you might have dropped a library on them.

                    Comment

                    Working...
                    X