anchor.diff:  It's when `StringBuilder.delete()` is called which calls `System.arraycopy()`.
   The issue is that 1 million characters need to be shifted in very small increments:
   
  -image:native-reference-perf-flamegraph-symbols.png[Perf flamegraph with symbols]
  +image::native-reference-perf-flamegraph-symbols.png[Perf flamegraph with symbols]
   
   === Multi-Thread
   
  
positive.code: Once the import completes (shouldn't take more than a couple of minutes), go to the Neo4j browser,
  and you'll be able to observe a small summary of the data in the graph:
  
  image:native-reference-neo4j-db-info.png[Neo4j database information after import]
  
  The data above shows that there are ~60000 methods, and just over ~200000 edges between them.
  The Quarkus application demonstrated here is very basic, so there’s not a lot we can explore, but here are some example queries you can run to explore the graph in more detail.
  
negative.code: ${FG_HOME}/flamegraph.pl out.perf-folded > flamegraph.svg
  ----
  
  image::native-reference-multi-flamegraph-joined-threads.png[Muti-thread perf flamegraph with joined threads]
  
  When you open the flamegraph, you will see all threads' work collapsed into a single area.
  Then, you can clearly see that there's some locking that could affect performance.
  