Navneeth,  Namespace access will not provide the same level of performance as when accessing an object using its Object ID. The underlying access method for Atmos is to use an object's Object ID. Namespace "names" are mapped to the Object ID and will therefore require a translation from "name" to Object ID. If your application is performance focused you may want to evaluate/test the tradeoff between using your own translation tables (name to Object ID) versus having Atmos do it for you.  Regards,  Dave 
Hello,  I have a question on using the namespace interface when manipulating objects: is there any difference, performance wise, in accessing, enumerating or reading out data via the namespace interface as opposed to using the Object Id of the object?  For example, if I've created several thousand objects (all via the namespace interface) in a complicated directory structure that is deep as well as broad, is it any faster to access these objects via their Object Id's rather than their namespace names?  Since we get the Object Id even when creating via the namespace interface, we (the client app) should be able to store this Id and use this for querying/reading if it is faster. However, if it makes no difference, then the client app need not store the Object Id and just use the namespace interface.  thanks, Navneeth
Performance: Object Id vs Namespace