• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Quartz/memory benchmarks...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Quartz/memory benchmarks...


  • Subject: Re: Quartz/memory benchmarks...
  • From: Kyle Hammond <email@hidden>
  • Date: Thu, 27 Jun 2002 16:23:41 -0500

I see what you mean about that code slowing down when the window gets larger.

However, I'm not really convinced. If I grab the scroll bar thumb and slide it up and down, the table scrolls very smoothly, even full screen. If I select a row and hold down the keyboard up or down arrow key, the table also scrolls very smoothly, as quickly as my key-repeat setting can go. If I click the scroll bar up or down arrows and hold the mouse button down, the table scrolls very quickly.

Users aren't going to be able to do what your programmatic scrolling is doing. They're going to have to use the scrollbar or arrow keys to scroll. So, I don't think that you can definitely say from this code that "Quartz is slow". The scroll bar may be using some optimized code path behind the scenes, but that's another issue. Quartz itself isn't the cause of the slowdown, since the scroll bar can make it zip right along.

The question is, what exactly is the scroll bar (NSScroller) doing that your programmatic scrolling is not doing? And for that answer, you'd have to talk to an Apple engineer.

Kyle

On Thursday, June 27, 2002, at 03:42 PM, Allan Odgaard wrote:
On torsdag, juni 27, 2002, at 05:32 , Kyle Hammond wrote:

I've found this thread to be fairly interesting, but am not seeing any of the slowness that has been talked about.

I should probably have provided some benchmarking code that people could check for themselves -- but the project in which my benchmarking evolved did a lot of other stuff, and it wasn't easy to isolate...

But now I have put together a simple TableView with 500 rows and 2 columns.

The program will setup a timer to call the scroll method 60 times pr. second. Every 25th invocation will measure the time since last, and based on this calculate a frames pr. second count.

So just run the program and enable "scroll programatically", then you'll see a fps which should be close to 60. Now try to make the window larger and see how it drops -- on my system it drops to 17-18 fps when the window fills my entire desktop (which runs at 1600x1024).

The archive is here: <url:http://www.top-
house.dk/~nr8/ScrollBenchmark.dmg.bz2>

Have fun...


---------------------
Kyle Hammond
email@hidden

http://www.CodeBlazer.com/ - multimedia software solutions
http://www.isd.net/dsl03002/ - my personal home page
http://cocoabudget.home.att.net/ - Budget for MacOS X home page
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Quartz/memory benchmarks...
      • From: Allan Odgaard <email@hidden>
References: 
 >Re: Quartz/memory benchmarks... (From: Allan Odgaard <email@hidden>)

  • Prev by Date: Re: Quartz/memory benchmarks...
  • Next by Date: Re: Quartz/memory benchmarks...
  • Previous by thread: Re: Quartz/memory benchmarks...
  • Next by thread: Re: Quartz/memory benchmarks...
  • Index(es):
    • Date
    • Thread