Performance of Thread.setName()

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Unresolved
    • Priority: P4
    • None
    • Affects Version/s: 27
    • Component/s: core-libs

      A user reported a performance issue where Cassandra spends significant amount of time in Thread.setName(). While it is perhaps silly of Cassandra to call Thread.setName() so often (apparently to represent often-changing thread states), there might an opportunity to improve performance of Thread.setName().

            Assignee:
            Roman Kennke
            Reporter:
            Roman Kennke
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: