Performance - Structures in an NSValue Object and Container

Question

In a situation where I need to save all data members in NSDictionary, does it make sense to invest in (my own NSValue) structures (custom types or even scalars, that is CGPoint)), so I can avoid the overhead of encoding / decoding it every time, when do i get or set a member?

For large structures (16 floats), the savings are significant for IMO. But even with CGPointI would save 4 bytes of copy, as well as encoding / decoding time.

Answer 1

? .

, CFDictionary , ++ std::map/std::tr1::unordered_map ( ++, ).

Answer 2

: . (, ) , .

Answer 3

, NSDictionary , NSDictionary. .