CopyPastor

Detecting plagiarism made easy.

Score: 0.9924461444218954; Reported for: String similarity Open both answers

Possible Plagiarism

Plagiarized on 2018-11-19
by An Nguyen

Original Post

Original - Posted on 2012-04-26
by Abizern



            
Present in both answers; Present only in the new answer; Present only in the old answer;

I think you're more likely to hit the performance limits on an iOS device before you hit any storage limits in Core Data. You'll also be getting a performance hit from pulling in large chunks of data.
You are better off, both in performance and manageability, breaking up large blocks of text into smaller chunks.



I think you're more likely to hit the performance limits on an iOS device before you hit any storage limits in Core Data. You'll also be getting a performance hit from pulling in large chunks of data.
You are better off, both in performance and manageability, breaking up large blocks of text into smaller chunks.
From what I remember Marcus Zarra telling me anyway.

        
Present in both answers; Present only in the new answer; Present only in the old answer;