Uploaded image for project: 'Code Tools'
  1. Code Tools
  2. CODETOOLS-7901240

Store benchmark metadata in distinct files

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Unresolved
    • Icon: P5 P5
    • None
    • None
    • tools
    • None
    • jmh

      CODETOOLS-7901237 highlighted the problem with regenerating the benchmark list with
      every benchmark generation session. While we have plunged the leak with benchmark generator
      re-reading the benchmark list and merging it, it might be cleaner to split the metadata file on per-benchmark
      basis, so that per-benchmark configuration would be normally overwritten without messing with anything else.

            Unassigned Unassigned
            shade Aleksey Shipilev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: