Timeout handling should be more aggressive

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Unresolved
    • Priority: P4
    • None
    • Affects Version/s: None
    • Component/s: tools
    • None
    • jmh

      Current timeout mechanics requires cooperation from the benchmarking code: it will basically issue interrupts to benchmark threads when the timeout is reached. Some users expect more aggressive shutdown when timeout is reached. Absent the way to stop the uncooperating thread, we can only shutdown the VM. We need to explore if this is doable and practical to do.

            Assignee:
            Unassigned
            Reporter:
            Aleksey Shipilev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: