I need to optimize UITableViewCell image loading

Question

I have a custom UITableViewCell. Each cell has an unique image.

I have an image loader class. I passed a dictionary to ImageLoader's method. A dictionary composed by image url and some other information. This code works well when we scroll down UITableView slowly. But if we scroll down rapidly it will have some lags. I need to optimize my algorithm. Any ideas.

- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath 
{
  [ImageLoader addImageToQueue:dictionary];
}

You're going to have to post more code than that!! – Ashley Mills May 28 '12 at 17:12 — Ashley Mills, May 28 '12 at 17:12
The code you posted does not seem to make sense as it is. – diegoreymendez May 28 '12 at 17:31 — diegoreymendez, May 28 '12 at 17:31

score 1 · Accepted Answer · answered May 30 '12 at 15:29

1

I believe that this tutorial would be useful in answering your question. It covers the reasons why you aren't able to scroll smoothly and how to fix it.

answered May 30 '12 at 15:29

THE DOCTOR

4,399
10
43
64

score 0 · Answer 2 · answered May 28 '12 at 17:36

Disable the image loading and test the table behavior - the problem might be a slow cell initialization, if the custom cell drawRect is overridden, pay much attention to this method as the documentation says it's navy usage slows the animations dramatically, find the way to optimize the drawing.
If the table scrolls smoothly with the image-loading disabled, consider to limit the number of the concurrent load operations (with the pending operations to be loaded later) and use caching whenever available.

CrimsonDiego · Answer 3 · 2012-05-28T17:49:14.450

Use UITableView dequeueReusableCellWithIdentifier:

This basically means that you don't have to recreate the table cell from scratch every time. If you give a cell a reuse identifier, it will keep ahold of that cell in memory and let you dequeue it when you ask for a cell matching that identifier.

Since every cell has a unique image, you'd probably be best off setting each cell's unique identifier as something from the image - perhaps the image's URL or filename. This will eat up more memory than disposing of and recreating the cells, but it reduces scroll lag, and if your images are small then the memory footprint isn't that large.

You'd probably end up with something like:

- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath 
{
    NSString *imageURL = urlOfImageForThisCell;
    UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:imageURL];
    if(!cell)
    {
        cell = [self makeNewCell];
        //if your reuseIdentifier is unique to each image, you only ever need to set it's image here
        cell.image = imageForThisCell;

        cell.reuseIdentifier = imageURL;
    }

    //additional cell setup here

    return cell;
}

You'll also want to look in subclassing UITableViewCell and overriding prepareForReuse.

score 0 · Answer 4 · answered May 28 '12 at 18:10

I would check out Ray Wenderlich's tutorial on Multithreading and GCD here.

It's hard without seeing your cellForRowAtIndexPath: or ImageLoader code but I have a suspicion that your ImageLoader is slowing things down to the point where it has to wait for it to complete before it provides the cell. Even if it's just reading the image from the disk, it should be done on the background thread, asynchronously so that the main thread can focus on scrolling smoothly.

Good luck!

score 0 · Answer 5 · answered Nov 15 '13 at 18:15

0

I know this is old, but I recommend this post: http://www.nsprogrammer.com/2013/10/easy-uitableview-buffering.html

answered Nov 15 '13 at 18:15

NSProgrammer

2,387
1
24
27

I need to optimize UITableViewCell image loading

5 Answers5