i see gabe
maybe give a try to MSI kombustor, they have single apps for single and multi gpu, maybe it will load both gpu better than furmark does.
Printable View
i see gabe
maybe give a try to MSI kombustor, they have single apps for single and multi gpu, maybe it will load both gpu better than furmark does.
yep, I missed that you used difference in water temp to filter out gpu idle heat from flow...I had not thought of doing that. I havent played around as much with testing as you have, I would have to test with just waterblock and no active gpu to confirm that changes in flow dont alter water temps in that circumstance, though you may have already done/know that.
btw...planning on any testing with 2 360 rads...one of the most common scenarios is 1 loop or 2 with 2 rads.
To test both fire up Furmark 1.8 for multi GPUs to get 100% gpu load. Furmark's affinity is already set to Core 0 only, so if you load your other cores with prime (or linx for max temps) as suggested you'll be able to generate a huge amount of heat dump. This is the only situation where my single loop struggles. You can even fire off super pi 32m on core 0 simulatenously to get 100% load on that too as furmark only gives about 33% load on core 0.
Several years ago i used to have very large and ugly watercooled rig with adjustable pump 30-45-60w. Changing pump power from 30 to 60w would lower the cpu temps only measely 1-2c. The water capacity and radiators were so large that water temp didnt raise due the higher pump power output.
The reason for this is that water has large heat capacity compared to cpu wattage. Its very easy to calculate too. The improvement is explained mainly with higher turbulence in the waterblock which makes the waterblock as a heat exchanger work sligtly better compared to low flow.
Gabe, with BOINC just connect to milkyway @ home. This can be set to use 100% GPU and then you can fold with your CPU as normal on WCG or whatever you like. I'm using two loops so I can fold GPU and CPU 24/7... This kind of test data would be very interesting to me since I have three 120.2 rads across two loops. :p:
Finally, great work on the data above and many thanks for sharing your findings. I found the data very concise and very informational. :up:
Yes it's another way to do it, but unnecessarily time consumming. The rise in coolant temp due to GPU heat is unequivocally showed by [(ΔT Water to Air test 2) - (ΔT Water to Air test 1)]; when substract this result from [(ΔT CPU air Test 2) - (ΔT CPU air test 1)], you isolate the rise in temp due to pressure drop, since its the only factor left.
This describes our Xtreme bench (also mentionned in the body of the article). Ppl have complained that it is too extreme. What we have done (not yet published though), is testing dual loops with a 320 and a 220. I am trying to test configurations that can be easily (without major mods) integrated inside of a case, which I believe represents what the majority of ppl would like to be able to accomplish. The very popular Cosmos S for example is capable of integrating a triple and a dual without any major mods.
I did already, and it is set to use the GPU, but all I get is 57% load on GPU #2. I need to reach 100% on both GPU's in order to have comparable results.
Thanks for this very nice test. :up: I would have expected to see better GPU temps with the vga blocks in series but your tests proved otherwise here. This conviced me to get a second d-plug to run my videocards parallel. I owe you a beer. ;)
Gabe: Thanks for the insightful and well-executed tests! :up:
I may be getting ahead of myself here, based on your comment above about upcoming results for a single vs. dual loop comparison; however, I recently upgraded my system and could use some advice in arranging my loops.
I have (1) quad radiator and (3) triple radiators in my Mountain Mods Ascension case at the moment. Combined with (2) of your MCP655 pumps, I am attempting to determine the optimal loop configuration to cool (1) i7 930 on a Swiftech XT waterblock and (2) EVGA GTX 480s with aftermarket waterblocks.
I currently have two dedicated loops (i.e. loop one is cpu only; loop two contains both GPUs in series seperated by a single triple radiator). All three triple radiators are in the GPU loop and the single quad is cooling the cpu loop.
Based on the results above, and a recent post Vapor made here, at which you had hinted some agreement, I am considering putting everything in a single loop with the GPUs in parallel. Perhaps all three in parallel?
I would be grateful for any help you, or any other knowledgeable XS member, could offer.
+1 for that :up:
My current loop is mcr320, xt, mcp650(still running after 5.5 years:shocked:), and microres v1, with 1/2 inch ID. The 320 is mounted with a radbox, and a bracket at the bottom, on the rear of my armor case.
I have an mcr220 that I'm thinking of adding internally at the front of the case, and a microres v2 (adding thermal sensor and BigNG) and mcp655 have been ordered.
So the question for me (once I finally order a block for my 5850) is one loop or two, since I'll have all the components for two.
Now to decide what to do with my old mcr120 and 3/8 gpu and chipset blocks! :p:
Nicely presented, useful data Gabe :up:
Thanks Gabe. Although it hasn't run 24/7, I know I'll feel better about the 5.5 year old mcp650 if it has a 655 backing it up. And the extra flow won't hurt! I do plan to monitor the flow with a T-Balancer set up to shut it down if there are any major changes.
May I suggest that an rpm lead on the 655 NON B would be most welcome?
I'm assuming that my old 120 probably wouldn't add much in that loop. I'm guessing part of the reason a 320/220 combo is common, is that people have parts leftover after upgrading. I know my upgrade path was 120->220->320.
And thanks for the value for the $ over the years. I should send you a pic of my homemade mcw6000 am3 bracket :rofl::ROTF: I just retired that block and replaced it with an XT :)
I never could understand reason for rpm lead to be soldered only on 655B/D5 non-vario. Of course, it's not too difficult mod to solder one for Vario, but why oh why more expensive pump should had that one feature less? I simply don't get marketing reasoning behind that.
Nice Gabe.
It's nice to see some real world testing to show that for most systems you don't really need dual loop setups.
It would be interesting to see some test results with the GPUs under load too.
Thanks for taking the time. :)
"GPU load tests: We used Furmark in extreme burning mode, windowed in 1920x1050, post processing off to enable 100% load to both GPU’s in SLI configuration, and logged the temperature results at 2 seconds intervals with GPUZ."
Gabe it said you ran the sli test windowed?
Do you remember @ CES i told you SLI will not work unless you full screen it?
And you did that and saw a difference in temps. Then you said Oh its fine.. let it run for a while.. and we walked away.
Gabe you need to run full screen on SLI setups like i showed you @ CES.
I dont think furmark changed this...
Windowed mode does not allow the GPU scaling to occure on direct 3d.
You need Fullscreen for gpu scaling to occur.
This is why u cant play with Xfire or SLI in windowed mode on games.
Unless you have a leak. When one of my loops got sabotaged I got lucky that the loop only cooled half the computer and not the entire thing otherwise it would have been much worse. :shakes:
This data is very useful and I must say that I will be using parallel on my multi part loops from now on. Although back in the day with my first wc rig I actually had parallel serial lol. Yes it was parallel to dual xeons then to serial for the motherboard and hard drives. The setup for that old system was so strange and had so much pressure I still can not believe that I pulled off decent temps off a single 120mm rad. Then again I had a 120+cfm fan on it :rofl: