{"id":218,"date":"2016-08-15T21:35:04","date_gmt":"2016-08-15T11:35:04","guid":{"rendered":"http:\/\/alrichardson.com\/?p=218"},"modified":"2016-08-15T21:35:14","modified_gmt":"2016-08-15T11:35:14","slug":"profiling-code","status":"publish","type":"post","link":"https:\/\/alrichardson.com\/?p=218","title":{"rendered":"Profiling code."},"content":{"rendered":"

I’ve been wondering lately, when it comes to finding nodes in a scene, nodes which may or may no exist, which will be faster?<\/p>\n

using a Try, Except?
\nor using maya’s built in objExists command?<\/p>\n

My theory was that the Try, Except would be faster as objExists would have to loop over all nodes in the scene. At least as far as I assume.
\nSo i put it to the test.<\/p>\n

The first thing I neede ws a profiler. A little googling and I turned up Pyhtons Timeit module.<\/p>\n

This can be imported using<\/p>\n

\r\nimport timeit\r\n\r\nprint timeit.timeit(function)\r\n<\/pre>\n
This will print the result of running the specified function one milling times. Its is run this many times to ensure consistency in the results.
\nThat can be reduced by adding the number flag, to specify how many times the code is run, so:<\/p>\n
\r\nimport timeit\r\n\r\nprint timeit.timeit(function, number = 10000)\r\n<\/pre>\n
This will run the code ten thousand times. Its quicker and consistant enough for my requirements.<\/p>\n
Getting into the problem at hand, I setup two functions, one as a Try, Except and another as objExists.
\nI ran each one in an empty scene and each one in a scene which included a complex character rig.
\nThe code and results are below:<\/p>\n
import maya.cmds as cmds\r\nimport timeit\r\n\r\ndef exists():\r\n    found = cmds.objExists('locator1')\r\n    return found\r\n\r\ndef select():\r\n    found = False\r\n    try:\r\n        cmds.select('locator1')\r\n        found = True\r\n    except:\r\n        found = False\r\n    return found\r\n\r\nprint timeit.timeit(select, number = 10000)<\/pre>\n
The results <\/p>\n
The Try, Except took:
\n0.398722180715 in an empty scene and
\n0.376243066404 in a complex rig scene<\/p>\n
where as the objExists took
\n0.0698589508479 in an empty scene and
\n0.0415636909748 in a complex rig scene<\/p>\n
astonishing, and, contrary to my expectations, the Try, Except took nearly ten fold longer than the objExists!
\nFrom this I learned: Using specific commands looks to be faster than using Try, Except! I’ll have to test more commands and find out :)
\nIf you’d like to try this code yourself, you can see the result for each funstion by changing this line:<\/p>\n
\r\nprint timeit.timeit(select, number = 10000)<\/pre>\n
To this:<\/p>\n
\r\nprint timeit.timeit(exists, number = 10000)<\/pre>\n
Cheers!<\/p>\n","protected":false},"excerpt":{"rendered":"
I’ve been wondering lately, when it comes to finding nodes in a scene, nodes which may or may no exist, which will be faster? using a Try, Except? or using maya’s built in objExists command? My theory was that the Try, Except would be faster as objExists would have to loop over all nodes in […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-218","post","type-post","status-publish","format-standard","hentry","category-maya"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t