Several things may be contributing:
1) If Extended Find is enabled on some of the ancestors of the object you are attempting to Add, TestComplete needs to do the "find" on those objects before it can proceed to add the object in question. Additionally, if extended find is enabled to be automatically applied under Tools | Options | Engines | NameMapping "Use extended find when possible", TestComplete may be attempting to do the find on the very object you are mapping. I would suggest turning off that option and populating some additional ancestor objects to your mapped tree to speed up this process.
2) It could be possible that some of the objects in the tree leading up to the one you are attempting to map may have the visible property set to "false". Again, under Tools | Options | Engines | NameMapping there is an option for "search for visible objects first". Turn that off and see if this improves mapping performance
3) By default, when a project is created, NameMapping stores images for controls upon mapping. As far as I can tell (and I could be wrong as I don't use this feature), storing images for mapped objects is simply a helpful too just to identify the object to the person creating a test case. It doesn't actually add any functionality or feature to the execution of tests. For this reason, I always turn off this feature as it does add to mapping time and takes up disk space and source control space. See the screenshot for where to turn this off
Thanks for the Reply, But i have taken care of all the parameters then too i am facing this challenge with Name mapping. Only there is one thing that my name mapping is huge and has most of the objects having extended find enabled.
The extended find is what is slowing things down, I'm fairly certain. You can try Novari-QA's suggestion. However, I think you're going to have to make the changes to eliminate some of the usage of Extended Find to speed things up.
