Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am debating whether or not to use SQLite for my app. I have to run through about 4k objects hundreds if not thousands of times per app session.
My question is, does anyone know if using a NSMutableArray will burn through the battery faster (because of processing) than it would if I were using SQLLite? Im almost sure it would save the battery just a tad bit at least.. but do you think the battery savings would be worth refactoring my code?
The answer to these questions is always the same – It depends entirely on what your objects are and what you are doing with them.
If your code runs fine then don’t mess with it. Premature optimization is the road to hell.
Also, if you are concerned about it, Apple provides great tools to measure these kinds of things. Use them – they will tell you far more about for particular case than anyone here can.