What steps will reproduce the problem?
(1) Build and run views_examples_with_content_exe
(2) Switch to the throbber example

What is the expected result?
Very little CPU to animate the throbber (ideally GPU-accelerated)

What happens instead?
There are two views_examples_with_content_exe processes for some reason in Activity Monitor. The first consumes 10% CPU, and the second 5% CPU.

Quartz Debug shows the 16x16 throbber running side of a 130x130 rect. Part of the excessive CPU is probably due to the larger-than-needed rect, but I suspect even a properly-sized throbber view will still consume excessive CPU.