mitch_de Posted March 21, 2013 Author Share Posted March 21, 2013 It seems that running OceanWave OpenCL on very lowend gpu - like AMD 4670 may fail! Its running out of some local memory, the bench needs. (shown in logs as an assest error) Other than running games, were to less VRAM produces little freezes (fps drops) by VRAM swapping, OpenCL needs enough free + unfragmented (one block!) onboard (VRAM) memory which cant be swapped like using OpenGL. OpenGL never can run put of VRAM - it only loose much speed / stalls. One more thing: The memory OpenCL uses must be in one block - so not all memory available for OpenGL is also available for OpenCL. For example an 512 MB card, running OS X desktop (uses little VRAM) uses already about 50 MB. You will not have the rest - 462 MB (512 -50) available for OpenCL tasks. Its less, i think fixed to some 32/64 MB "slots" like 384 MB or 328 MB and or reduced by some VRAM fragments. Even the GPU has 512 MB the bench may fail in case of AMD 46xx gpus - some internals (memory management) maybe incompatible with complex OpenCL benches. Also the OS X driver may have an bug which reports wrong AMD 46xx features which this benchmark reads out and uses them. But it doesnt matter real, because CoreImage for that GPU is OK and OpenCL will never perform well on AMD 46xx gpus. This bench make more sense AMD 48xx and up. COOL , first bench results (lots) for new AMD 7950 Mac by Rob - barefeats!! http://www.barefeats.com/gpu7950.html Link to comment Share on other sites More sharing options...
eep357 Posted March 22, 2013 Share Posted March 22, 2013 Eep357, differ from who/what? That was precisely my point, thus my surprise seeing nVidia benching higher in this topic. But i think mitch_de explained things quite well. Sorry! I hadn't noticed Nvidia benching higher, was looking only at the "pole position" on page 1 where it got stomped And above graph where only Nvidia cards in SLI were able to top single AMD. Kinda figured below that, it all depends on cards age who score best. Link to comment Share on other sites More sharing options...
MakeMineMac Posted May 4, 2013 Share Posted May 4, 2013 Hi all, Just put in the GTX 660 it is working great, however, I cannot get OpenCL to work. I came from the dreaded 560ti to this card and now no OpenCL! For your information my kexts all have the 3/10/13 date on them and say version 8.10.44 (I assume this is the native Apple 10.8.3 kexts???) GraphicsEnabler=No MacPro 4,1 I still have one 560ti in the lower slot, (that shouldn't matter) This has to be something simple, what on earth am I doing wrong? Please let me know if I need to change frameworks as well as kexts as I am not too sure, so far I have been keeping the frameworks with their corresponding kexts...if that makes sense. Like I said, card(s) are working great, just no OpenCL on the GTX 660, thought it would be an easy swap, just put the card in, put the original unmodified kexts back, and everything should work. Knew it would be harder than that.... 1 Link to comment Share on other sites More sharing options...
fau7i Posted May 11, 2013 Share Posted May 11, 2013 First time I got no error. In fact, I have to turn off HD 4000 to get this scores. Link to comment Share on other sites More sharing options...
k3nny Posted June 11, 2013 Share Posted June 11, 2013 Test with 10.9 DP1: FPS is locked at ~60. Probably an issue with VSync? Link to comment Share on other sites More sharing options...
stefano.85 Posted June 11, 2013 Share Posted June 11, 2013 Test with 10.9 DP1: FPS is locked at ~60. Probably an issue with VSync? +1 same here... on first system in signature Link to comment Share on other sites More sharing options...
mitch_de Posted June 12, 2013 Author Share Posted June 12, 2013 MY 9600 GT getting 94 FPS (on 60 Hz TFT, same as 10.8) with 10.9 DP1 - so perhaps other problem (driver dependend, gpu type depended) Link to comment Share on other sites More sharing options...
gils83 Posted June 30, 2013 Share Posted June 30, 2013 OS X 10.9 DP2 Link to comment Share on other sites More sharing options...
mitch_de Posted July 1, 2013 Author Share Posted July 1, 2013 PS: With OS X 10.9 lots of gpus (not my 9600 GT) running in an 60 FPS (VSYNC?) bug gap. Link to comment Share on other sites More sharing options...
RobertX Posted October 7, 2013 Share Posted October 7, 2013 ...@mitch_de ...got that issue here using the GM Link to comment Share on other sites More sharing options...
fau7i Posted October 23, 2013 Share Posted October 23, 2013 In Mavericks GM, same issue. And, Tahiti becomes FirePro Link to comment Share on other sites More sharing options...
XanthraX Posted October 23, 2013 Share Posted October 23, 2013 Mavericks 10.9 on Gigabyte GA-B75M-D3H, CPU: Intel® Pentium® Processor G645 (3M Cache, 2.90 GHz), Graphic card: Asus EAH5670 (AMD Radeon HD 5670, GDDR5 1GB) Link to comment Share on other sites More sharing options...
DanMcQ Posted October 23, 2013 Share Posted October 23, 2013 Running 10.9 Build 13A603 on a Gigabyte GA-Z77X-UP5-TH, GTX650, Core i7 3770k @ 3.5ghz Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 23, 2013 Share Posted October 23, 2013 my gtx580 is locked at 60 fps too with maverix Link to comment Share on other sites More sharing options...
tbp Posted October 25, 2013 Share Posted October 25, 2013 my gtx580 is locked at 60 fps too with maverix Same here with GTX 660. Open GL bench tests also went down maybe 3-5% with maverix. Luxmark wont work. Link to comment Share on other sites More sharing options...
dbm Posted October 28, 2013 Share Posted October 28, 2013 Yes i would agreed with it aswell, on gtx 560 ti its stuck at 60 fps. Link to comment Share on other sites More sharing options...
mitch_de Posted October 28, 2013 Author Share Posted October 28, 2013 60 FPS has to do with 10.9 AND kind of GPU. My 440 GT (NVDAGF100Hal) hasnt that effect even running 10.9 on 60 Hz tft (getting 105 FPS). Perhaps some Nvidia driver bug using vsync even if programm disable that. Link to comment Share on other sites More sharing options...
shiecldk Posted November 12, 2013 Share Posted November 12, 2013 HD6850 is locked at 60fps too. I guess it might has something to do with Maverick's energy-saving feature. @mitch_de When I put a window cover the Oceanwave app, the score will boost back. 1 Link to comment Share on other sites More sharing options...
RobertX Posted November 18, 2013 Share Posted November 18, 2013 HD6850 is locked at 60fps too. I guess it might has something to do with Maverick's energy-saving feature. @mitch_de When I put a window cover the Oceanwave app, the score will boost back. same...window covered , back to normal scores Link to comment Share on other sites More sharing options...
npwski Posted November 20, 2013 Share Posted November 20, 2013 GTX Titan oc'ed @1132, OS 10.9 /13A603 This 60 fps - with default settings:As I understand, it's because refresh is locked. This 969 fps - with option "BeamSync=Disable" (Quartz Debug.app)I don't know, this result is correct or not. May be is there other way to disable vsync? Link to comment Share on other sites More sharing options...
iaihc Posted November 20, 2013 Share Posted November 20, 2013 Thanks you! GT540M=83 Link to comment Share on other sites More sharing options...
beasty uk Posted November 20, 2013 Share Posted November 20, 2013 Well the debug app fixed my score 280fps from 60 but fcpx runs great without this app i think it only gives you better ocean wave score Link to comment Share on other sites More sharing options...
gils83 Posted November 20, 2013 Share Posted November 20, 2013 Link to comment Share on other sites More sharing options...
PoisonApple666 Posted November 21, 2013 Share Posted November 21, 2013 what is :\"window covered" and the "quartz debug" app?? Link to comment Share on other sites More sharing options...
beasty uk Posted November 21, 2013 Share Posted November 21, 2013 You just drag a window over the benchmark when its going and it speeds up from 60fps to the right fps. And the other is an app you can click disable beam sync and it sorts the score out without a window. And thats all the 2 things do is make the fps right in ocean wave nothing else. I thought it would make mavericks run smoother but it does not lol Link to comment Share on other sites More sharing options...
Recommended Posts