Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-5422

Native protocol sanity check

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 1.2.6
    • Legacy/CQL
    • None
    • Normal

    Description

      With MutationStatement.execute turned into a no-op, I only get about 33k insert_prepared ops/s on my laptop. That is: this is an upper bound for our performance if Cassandra were infinitely fast, limited by netty handling the protocol + connections.

      This is up from about 13k/s with MS.execute running normally.

      ~40% overhead from netty seems awfully high to me, especially for insert_prepared where the return value is tiny. (I also used 4-byte column values to minimize that part as well.)

      Attachments

        1. 5422-test.txt
          4 kB
          Jonathan Ellis
        2. ExecuteMessage Profiling - Call Tree.png
          276 kB
          Daniel Norberg
        3. ExecuteMessage Profiling - Hot Spots.png
          212 kB
          Daniel Norberg

        Activity

          People

            danielnorberg Daniel Norberg
            jbellis Jonathan Ellis
            Daniel Norberg
            Sylvain Lebresne
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: