Jump to content

Profiling the plugin.


Recommended Posts

Hello, What is the best way to proceed for profiling the code? I'm using the built-in profiler in VS2010 without no luck. When I start the profiling session (CPU sampling) the report is showing me the time Houdini  spends in all the dlls, like the graphics drivers, or the opengl driver, instead of showing me the time spent in each function of the custom plugin.

 

When doing the instrumentation, VS opens Houdini with the default scene. That's it.

 

I could use the random-pausing technique but the code ends so fast (0.1 s) that I'm unable to get any useful sample.

 

I haven't found any post related to profiling code neither here or in SESI forums.

 

Thanks in advance

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...