News for hackers. Stuff that matters.
Re:Date parsing performance on iOS (NSDateformatter vs sqlite) by MishraAnurag on Saturday September 07, 2013 @10:16AM (#6345133)
A link to the source code is present in the article. You can find it here - https://gist.github.com/AnuragMishra/6474321

The NSDateFormatter is already being cached. That was my first suspicion on finding this issue too. We are using one formatter per thread in the production code, but that doesn't apply for the code I've posted since everything is done on the main thread using a single formatter instance.

Re:Date parsing performance on iOS (NSDateformatter vs sqlite) by asveikau on Saturday September 07, 2013 @12:37PM (#6345540)
sqlite happens after the objc version. Are the results any different when the sqlite code comes first? Actually the fairest comparison would be to store the dataset in a file, and have a process for timing NSDateFormatter, and a different one for testing sqlite. This would eliminate any advantage that a warm cache might give you.