Register    Login    Forum    Search    FAQ

Board index » Swiftech Communications » Theory & Practice

Post new topic Reply to topic  [ 3 posts ] 
Author Message
 Post subject: Dual Loop versus Single, the facts
 Post Posted: June 30th, 2010, 2:20 pm 
User avatar

Joined: January 24th, 2007, 4:35 pm
Posts: 258
Location: Lakewood, CA
The following series of tests represent Part II of the white paper published [url=""]here[/url]

In this article, the question we wanted to answer was:

Are dual (dedicated) loops better than single loops?


  • Loop 1: MCR320 Drive radiator, with built-in MCP355 pump, and an Apogee XT waterblock; the loop uses ½ lines. The fans are Gentle Typhoon’s (D1225C12B5AP-15) running at 1850 rpm and rated at 28 dB.
  • Loop 2: MCR220 Drive radiator, with built-in MCP355 pump,Gentle Typhoon fans (same model) and 1/2" lines.
  • All components are connected to the loop with CPC quick-disconnect fittings; they are fairly restrictive, but the time they save in changing setups overshadows any other considerations.
  • The CPU is an early Ci7 920, Revision C0/C1 stepping 4.
  • The Graphic cards are (2) EVGA GTX470 FTW
  • The Motherboard is a Gigabyte EX58-UD3R, and the OS is Windows 7 Ultimate 64 Bit.


  • The CPU maximum stable overclock was well established, since we have been using this same 920 ever since its introduction. It is 4095 Mhz (Intel Turbo mode on, and HT enabled), at 1.424v (after droop).
  • The GPU’s maximum stable overclock was established in the previous graphics tests using Furmark in extreme burn mode at 1920x1050 for a minimum of two hours, and further validated by running 3D Marks Vantage.
  • Max stable overclock for 2 cards in SLI was 825 MHz core and 1000 MHz memory, @1.087 Volts.

We conducted two series of tests, reflecting the following hardware configurations:
  • Series I, with the Ci7 920@ 4.1Gb and (2) GTX470 FTW in SLI @825/1000, and
  • Series II, with the Ci7 920@ 4.1Gb and (1) GTX470 FTW @825/1000.

Within each series, we tested three cooling loop configurations:
  • Dual Loop with MCR320 Drive dedicated to cooling the CPU, and MCR220 Drive dedicated to cooling the GPU(s)
  • Dual Loop with MCR220 Drive dedicated to cooling the CPU, and MCR320 Drive dedicated to cooling the GPU(s)
  • Single loop combining MCR320 Drive, MCR220 Drive, CPU, and parallelly linked GPU's, in series

Within each loop configuration, we simulated three load scenarios consisted in:
  • CPU load tests: In order to maintain consistency with previous test data, we ran our usual 8 instances of BurnK6. We logged the temperature results at 2 seconds intervals using CoreTemps. The average temperature of the 4 cores is reported.
  • 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.
  • Combined CPU + GPU load test: We used (7) instances of Burn K6 + Furmark in extreme burning mode - The combination of these two benchmarks placed ~100% load on all four CPU cores, and a load on both GPU cores varying between 98 and 100%.
  • Graphics cards were hydraulically linked in parallel, as a result of the findings outlined in part I of this article.

The test results are compiled and summarized in two groups: Temps under load in typical computer use, and Temps under load in Extreme computer use.

  • Typical computer use reflects the assumption that at the time of this writing, CPU maximum load and GPU maximum load are in the vast majority of the cases mutually exclusive of each other. In other words, the majority of games placing a heavy load on the GPU's use very few CPU resources, whereas the majority of CPU intensive applications use very little GPU resources.
  • The extreme computer use scenario reflects the currently rare occurrences where both CPU and GPU(s) are under maximum load.
  • Comparing these two groups provides an insight on the respective device load ratios relative to the heat exchangers and may provide guidance for further system configurations.

Environmental Temperature recording:

  • Air temperature: each fan was equipped with a type T Thermocouples (accurate at +/- 0.1c) at the inlet, and the average of the 3 values is reported.
  • Coolant temperature was measured at the radiator inlet with a Type T thermocouple (accurate at +/- 0.1°C).

Series 1 test results, CPU + SLI configuration:




Under typical computer use, the above test data suggests as a general rule that users would not benefit from setting up dedicated loops for CPU and GPU. Serializing pumps in the same loop also adds a redundancy factor that dedicated loops cannot provide. With superior reliability and lower temperatures at both CPU and GPU levels, single loops appear to win hands down.

Under extreme computer use, this setup recorded a notable advantage at the CPU temperature level for the dual loop, counterbalanced by the opposite effect at the GPU level. This extreme environment uncovered the critical importance of the respective load ratios generated by CPU class devices vs. GPU class devices, relative to the heat exchangers to which they are connected. Clearly, a CPU generating 150 Watts solely dedicated to a triple radiator will cool substantially better than when mixed with another 400 watts generated by two GPU's even with a second dual radiator in the loop. Jedi Masters would say, "we need to bring balance to the force here", and they would be right.

We could define a simple mathematical method to properly configure a system accounting for loads, but that will be for another article. For now, we can simply illustrate the above in real life testing by removing one of the GPU's from the system. It has for effect to balance the heat load generated by CPU device more evenly against that of the GPU device and demonstrates how load ratios affects the results:



What we see above is that even under extreme use, the dual loop has all but lost its performance advantage against the single loop. Incidentally, the same type of trend could have also been obtained by adding a second CPU in the loop instead of removing a GPU.


Under extreme performance scenarios, and from a pure performance standpoint, dual loops versus single loop are neither better nor worse, under the strict condition that the load ratios are evenly balanced.
Under the most commonly encountered loads though, single loops do win.

Under both of the above use scenarios, single loops also win from a reliability standpoint because of pump redundancy.

The choice is yours to make.

 Post subject: Re: Dual Loop versus Single, the facts
 Post Posted: May 28th, 2012, 1:55 am 

Joined: May 25th, 2012, 2:35 am
Posts: 0
Thanks a lot for this post!
That's truly exciting!

Try this pdf viewer

 Post subject: Re: Dual Loop versus Single, the facts
 Post Posted: June 18th, 2015, 1:46 am 

Joined: June 18th, 2015, 12:56 am
Posts: 0
I apologise, but, in my opinion, you are not right. Let's discuss. Write to me in PM, we will communicate.


Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

Board index » Swiftech Communications » Theory & Practice

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to: