Will loading a NSMutableDictionary slow down my application to the point that it might be a problem? I was planning on having around 1100 entries in the Dictionary, and would like to know if this is a problem worth worrying about. If it is, I was planning on separating the dictionary into a few different sub-dictionaries. The Dictionaries have a string for both the key and the value. I'm also planning to running this on a 2nd or 3rd generation iPad.

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.
If this question can be reworded to fit the rules in the help center, please edit the question.

This would be useful information... I am looking at implementing an NSDictionary as a big part of the app i'm working on right now.
–
CraigAug 2 '12 at 18:02

It sure will. You will get the best performance out of your app if it returns 0 from main() immediately. Seriously, though, the only way to answer this is for you to measure -- is the user experience affected? If so, use Instruments to find places to improve. Lather, rinse, repeat.
–
Josh CaswellAug 2 '12 at 19:49

Thanks, I was really just trying to get an idea before I get too far. The strings will likely only be a few characters (Username and Password). For the moment I was just planning on essentially loading them into memory to add a new entry (using plist).
–
An0r4kAug 2 '12 at 18:21

No problem but what you are doing does not sound very secure! Why do you store over 1.000 user passwords in a plist on the device?
–
user1567896Aug 2 '12 at 18:28