With the new retina macbooks, the screen resolution is 3 times greater than say a 1680*1050 display for older machines. If you’re doing a lot of per-pixel calculations with shaders such as gaussian blurs and such, it’s conceivable that you could be fill-rate bound, which means your graphics card could have trouble keeping up with all of the pixels it needs to push. I’ve not used a reina display machine personally and I haven’t seen your patches, so I can only speculate. Apple is pushing the limits of what GPUs can do with the retina display.
Some questions for you. Are these fullscreen renderings? If you change the output resolution, do things speed up? If yes is the answer to both questions, I would say you’re fill-rate bound. If not, it would help to see some examples to further diagnose the problem.
Yes it does. It seems that slow downs are intermittent. I can’t figure out the reason. One thing I am debating that the issues are caused by Mountain Lion GL pipeline. Apple has screwed up the CI. In my Quartz Composer patches the hit is around 30%. I had to return Macbook Pro Retina, but I will have to get it again in two weeks. Btw 2.7 high config is a waste. 2.6 should be good enough
Thank you, for the work on the images. I am trying to figure out rendering pipeline for creating 6000 X 4000 images