Is IKImageView volatile?

Question

I have an IKImageView and I put CGImages on it (which I am doing from NSImages). However, a typical 200DPI 8.5 / 11 page takes about 3 seconds to appear in rectangles of about 2 inches (screen) sideways at a time. This is really annoying. Is there any way around this?

Alternatively, is there a way to double the view buffer? To have 2 IKImageViews and paste into one and then display it?

ETA: doubling my scrollviews (given ikimageviews inside) and then painting them and then hiding them doesn't seem to help ... or maybe it helps a little, but not much

I made fun of the tools a bit and found that memcopy does a lot of work:

  22 commpage [libSystem.B.dylib] 78.0  __memcpy
  21 ImageIO 37.0  CGImageReadGetBytesAtOffset
  20 ImageIO 37.0  CGImageReadSessionGetBytes
  19 ImageIO 37.0  myTIFFReadProc
  18 libTIFF.dylib 37.0  TIFFReadRawStrip1
  17 libTIFF.dylib 37.0  TIFFFillStrip
  16 libTIFF.dylib 37.0  _cg_TIFFReadEncodedStrip
  15 ImageIO 37.0  copyImageBlockSetTIFF
  14 ImageIO 37.0  ImageProviderCopyImageBlockSetCallback
  13 CoreGraphics 37.0  CGImageProviderCopyImageBlockSet
  12 CoreGraphics 37.0  img_blocks_create
  11 CoreGraphics 37.0  img_blocks_extent
  10 CoreGraphics 37.0  img_interpolate_extent
   9 CoreGraphics 37.0  img_data_lock
   8 CoreGraphics 37.0  CGSImageDataLock
   7 libRIP.A.dylib 37.0  ripc_AcquireImage
   6 libRIP.A.dylib 37.0  ripc_DrawImage
   5 CoreGraphics 37.0  CGContextDrawImage
   4 ImageKit 37.0  -[IKImageLayer drawInContext:]
   3 QuartzCore 37.0  tiled_layer_render(_CAImageProvider*, unsigned int, unsigned int, unsigned int, unsigned int, void*)
   2 QuartzCore 37.0  CAImageProviderThread(void*)
   1 libSystem.B.dylib 37.0  _pthread_wqthread
   0 libSystem.B.dylib 37.0  start_wqthread

I'm not sure what this tells me, though ...

EDIT: - . , quickdraw. 300%, = , , STILL .

, , 10.3 G5, Intel. , , 10 .

Answer 1

200DPI 8,5/11 .

, RGB, 11,22 . , 3,74 ( ) .

2 ()

. , 2 , 72 dpi . 144 , 144 × 144 .

, , , , .