The Starry Night, 278 :: home :: |
Late Winter Benchmarks
|
CPU Only |
GTX 960 |
GTX 1660 Super |
1k x 1k, 32-bit, PI benchmark | 1. BlurX: 13.693 2. BlurX: 13.625 3. NoiseX: 21.628 4. Starnet: 8.743 Total (2, 3, 4): 43.996 |
1. BlurX: 16.367 |
1. BlurX: 14.961 |
1600MC 32-bit XISF | ||
1. BlurX: 180.07 2. BlurX: 175.34 3. NoiseX: 172.18 4. Starnet: 157.76 Total (2, 3, 4): 505.28 |
1. BlurX: 53.979 2. BlurX: 44.660 3. NoiseX: 52.157 4. Starnet: 41.793 Total (2, 3, 4): 138.61 Speedup: 3.6x |
1. BlurX: 21.218 2. BlurX: 21.066 3. NoiseX: 20.094 4. Starnet: 33.021 Total (2, 3, 4): 74.181 Speedup: 6.8x |
R6, 16-bit TIF |
||
1. BlurX: 191.36 2. BlurX: 190.81 3. NoiseX: 172.13 4. Starnet: 102.20 Total (2, 3, 4): 465.14 |
1. BlurX: 48.890 2. BlurX: 48.273 3. NoiseX: 54.111 4. Starnet: 44.315 Total (2, 3, 4): 146.699 Speedup: 3.1x |
1. BlurX: 23.162 2. BlurX: 23.282 3. NoiseX: 31.592 4. Starnet: 35.861 Total (2, 3, 4): 59.195 Speedup: 7.86 |
R6, 32-bit XISF |
||
1. BlurX: 203.69 2. BlurX: 203.50 3. NoiseX: 180.64 4. Starnet: 111.88 Total (2, 3, 4): 496.02 |
1. BlurX: 51.735 2. BlurX: 52.480 3. NoiseX: 57.607 4. Starnet: 49.707 Total (2, 3, 4): 159.794 Speedup: 3.1x |
1. BlurX: 36.057 2. BlurX: 23.303 3. NoiseX: 32.126 4. Starnet: 35.895 Total (2, 3, 4): 91.3 Speedup: 5.44 |
SPECS & Caveats: The computer is an HP Envy 850-063 prebuilt (c. 2016) with an i7-5820k CPU capable of overclocking (see previous page). It's running at its factory-default speed (in this case, the "36x Default" profile in the HP Extreme Tuning Utility). It has 32GB of RAM, 6GB of which are assigned as a RAMdrive for PixInsight's swap files. There are 12 paths to the swap directory (one for each thread in the hexacore i7 CPU). I'm running PI 1.8.9-3. BlurX and NoiseX are Russell-Croman's BlurXterminator and NoiseXterminator respectively. Starnet++ is a PixInsight process. All defaults have been accepted for BlurX and NoiseX. Starnet++ is set to non-linear data; all other parms are default values. In one case, I noticed that a second invocation of BlurX ran much faster than the first. So I adopted the convention of running that routine twice and tallying only the second timing (go figure). The image source files are sitting in the C:/!pwork directory on the SATA3 system disk which is a 2TB Samsung 870 EVO SSD. This GTX 960 is an HP branded variant of an Nvidia-based graphics card supplied with the computer all those years ago. This GTX 1660 Super is also an HP variant first offered about three years later. Both graphics cards' specs appear identical to non-HP versions in terms of clock speed, RAM, chip-types, etc. If I could think of anything else that might be relavent, I'd include it.
Note that using the GTX 960 roughly triples processing speed. It's a hugely important speedup that makes all the difference in interactive workflows. Clearly it's not just the GPU processsor that determines the degree of improvement: bandwidth to move data on and off the card matters; the smallest images show the smallest improvements, etc. Anticipating the GTX 1660S: the clock speed is increased by 50% over the GTX 960; there are roughly 30% more CUDA cores; the GPU is upgraded; and the data path is broader. I'm expecting another factor of 3 and hoping for more (of course). Getting these processes down to just several seconds rather than ~1 minute would make another big difference when tweaking parms to produce improved images. I opted for a refurbished 1660S (thanks, eBay) rather than a more modern, more powerful graphics card to avoid having to upgrade the computer's power supply. The 1660S requires essentially the same power as the 960 (approximately 125W vs 120W) while other affordable options need 2-3x as much. This computer uses a standard ATX power supply, so if and when the day comes that an even more potent graphics card needs to live here, it should be relatively easy to boost the wattage. But first, the 1660S... Stay tuned.
So: the 1660S did not provide as spectacular an improvement over the 960 as I had hoped, but it's not bad, the price was right, and the exchange only took a few minutes (plus hours trying to readjust the color, but that's another story; and getting the sound back on, but that's still another story -- all is well enough). BTW, to tweak the color, the easiest way is via the Nvidia Control Panel (right click on the desktop, select the NvCP and "adjust desktop color settings" and there you go).
:: top ::