Depth-Anything VS async-profiler

Depth estimation improved a lot as well e.g. with Depth-Anything [0]. But those are mostly relative depth instead of metric. Also when even converted to metric they still seems have a lot of pointclouds at the edges that have to be pruned - visible in this blog [1]. Looks like those models trained on Lidar or Stereo depthmaps that has this limitations. I think we don't have enough clean training data for 3d unless we maybe train on synthetic data (then we can have plenty, generate realistic scene in Unreal Engine 5 and train on rendered 2d frames)

[0] https://github.com/LiheYoung/Depth-Anything

[1] https://medium.com/@patriciogv/the-state-of-the-art-of-depth...

Very interesting work! More details here: https://depth-anything.github.io/

It seems better overall and per parameter than current work, with relative and absolute measurement.

Is there any research people are aware of that provides sub-mm level models? For 3D modeling purposes? Or is "classic" photogrammetry still the best option there?

We'll use async-profiler and flame graphs for profiling. To simplify the process, we'll run the code using JBang.

JIT'ed code is sadly poorly supported, but LLVM has had great hooks for noting each method that is produced and its address. So you can build a simple mixed-mode unwinder, pretty easily, but mostly in process.

I think Intel's DNN things dump their info out to some common file that perf can read instead, but because the *kernels* themselves reuse rbp throughout oneDNN, it's totally useless.

Finally, can any JVM folks explain this claim about DWARF info from the article:

> Doesn't exist for JIT'd runtimes like the Java JVM

that just sounds surprising to me. Is it off by default or literally not available? (Google searches have mostly pointed to people wanting to include the JNI/C side of a JVM stack, like https://github.com/async-profiler/async-profiler/issues/215).

debugging native calls in itself is also painful. I have switched to using async-profiler (https://github.com/async-profiler/async-profiler) instead of JFR for most of my usecases.

A. it tracks native calls by default

https://github.com/async-profiler/async-profiler#flame-graph...

Ok, Windows is not supported. But IntelliJ made a fork which works on Windows.

Hi, today I used async-profiler to check the CPU usage of my Spring Boot app (just a normal backend) in production. Surprisingly, Lettuce (Redis) + Mybatis (MySQL) take up most of the CPU time. I am not talking about wall time here, but CPU time, since I know database requests need to wait for milliseconds and thus wall time will be very long. Therefore, I wonder:

You can use async-profiler to see what is happening under the hood.

I have used visual vm quite a bit. https://github.com/async-profiler/async-profiler is also amazing... Throw the binary on the system and fire it up. It also profiles down into native code as well if you do that kind of thing.