You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On macos, I don't think running perf is entirely easy (see docker/for-mac#5500, since I don't control he VM host's kernel version, it would be best if the perf package came from the same source...).
However, it seems that vtune supports macos. But, I find that it's not an option for wasmtime-go -- Is there an underlying reason for this?
Thanks!
The text was updated successfully, but these errors were encountered:
Unfortunately I don't really know. You can use Instruments.app to profile everything but jit code, but you probably want to profile jit code. I have never used vtune myself, so I don't know how well it works.
@srenatus Thanks for bringing this to our attention and sorry for not noticing this issue earlier. This initial patch was targeted and tested for ubuntu linux simply because it is a platform popular with many Vtune users. I'd say though that where Vtune runs and is an important for profiling, I think adding/accepting more support for those platforms would certainly be welcome.
I've been going through the docs on profiling wasm executions using wasmtime, and they state that there's perf and vtune.
On macos, I don't think running perf is entirely easy (see docker/for-mac#5500, since I don't control he VM host's kernel version, it would be best if the perf package came from the same source...).
However, it seems that vtune supports macos. But, I find that it's not an option for wasmtime-go -- Is there an underlying reason for this?
Thanks!
The text was updated successfully, but these errors were encountered: