Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Are you certain that the images are your issue? Have you done an alpha check on your table? In my experience, loading images is almost never the performance it for table scrolling, it is almost always alpha channel issues.</p> <p>I would turn on the alpha test in Instruments first before going down this road.</p> <h2>Update</h2> <p>I wonder if your loading into data first is a hinderance:</p> <pre><code>UIImage *userImage = [UIImage imageWithContentsOfFile:imageLocalPath]; [cell setAvatarImage:userImage]; </code></pre> <p>That <em>should</em> let <code>UIImage</code> do some caching work for you.</p> <ul> <li>Where are you getting the imageLocalPath? </li> <li>Is that stored in a Core Data entity or is there a calculation going on? </li> <li>What happens when you run this through shark?</li> <li>What FPS are you getting in Instruments on the device?</li> </ul> <h2>Update 2</h2> <p>Why are you taking Core Data objects and storing them into an <code>NSArray</code>? You should be using a <code>NSFetchedResultsController</code> in most situations.</p> <p>You should not be constructing the filePath, that takes time and <code>-componentsSeparatedByString:</code> is doing a string search; very slow. <strong>Store</strong> the file path when you save the image. Much faster. If you don't want to change your model, make it a transient value that is resolved on <code>-awakeFromFetch:</code>.</p> <p>The functions of Shark are integrated with Instruments as of iOS4. </p> <p>25-30 FPS is not ideal but is pretty good. That means you are getting good frame rate and minor tweaks (as to major fundamental issues) will probably get it higher.</p>
    singulars
    1. This table or related slice is empty.
    1. POCached UIImages fetching performance in UITableView
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMarcus S. Zarra
    1. USMarcus S. Zarra
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAll my tableviews are green. That's a nice test though. Thanks anyway.
      singulars
      1. PO
      1. USsamvermette
    2. COI am willing to bet that loading the images is still not the cause of the performance issue. Since your tableview is green then the next step would be to pre-load the images and see if that makes a performance difference, if it doesn't (as I suspect) then you can cross it off the list.
      singulars
      1. PO
      1. USMarcus S. Zarra
    3. COI just tested the scrolling with preloaded images (for the 2nd time) and scrolling dramatically improves. My question was specific to the image caching/fetching because I already had conducted both the alpha/opaque and the preloaded image tests (although I might have missed one).
      singulars
      1. PO
      1. USsamvermette
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload