Excellent shot.
If you enjoy night sky photography, you need to make your way here to Australia. A lot more stars, and a lot less light.
The photos you can take in the desert areas around Alice Springs and of Western Australia during the new moon are pretty much light pollution free.

Here is a teaser...

If they Naruto run to rush the base, only the out of shape finite fans will "run faster" than if they run normally (placebo effect).

Bad news: both techniques are much slower than electrical discharges, gaz canisters or high velocity bullets.

According to the event, titled, “Storm Area 51, They Can't Stop All of Us,” a group of alien hunters will meet at 3 a.m. on Sept. 20 near the top-secret U.S. Air Force Base to coordinate a plan of attack to reveal the truth behind the curtain. From there, the group will “Naruto run” with their arms stretched behind them like Naruto Uzumaki in the Japanese anime series “Naruto,” and therefore “move faster than their bullets.”

I think the consensus we've arrived at today in this and other threads is that a Pascal card should probably stick to the CUDA90 application. Which means a minimum of 384 series drivers but not to exceed the 410 series drivers for best performance. The -nobs will help put no matter which driver as long as you have enough cpu cores to support the gpu task.

Glad you found us, Brian. As for the definition of idling, there is that rumbling, crunching IRCer setting the Number crunching thread ablaze that is presently reshuffling the cards. Never trust sleeping waters, i guess :)

AWESOME that we have irc, almost made a post asking if we did! Just joined the irc4fun channel, I'll idle in there :)

I'll check back in with you tomorrow. The 24 hour penalty box should be expired by then and you should start receiving CUDA60 gpu tasks. I am really curious how the old zi3v code works on the early Maxwell gpus. I can't see how the performance could be any worse than the SoG application. If you are using the cmdline I stuck into the app_info, you have a unroll value of 6. The docs say that is the likely maximum. You might have to play with that and might find reducing to 4 or 2 might process faster. I also stuck in the -nobs parameter which speeds up gpu tasks by using a full cpu core to support the gpu thread. You have 8 cpu cores in the FX. I would limit the max cpu usage to 80% or put in a max_concurrent statement in an app_config for the project. Or set up the app_config for reserving a cpu core for each gpu task

<app_config>
  <app_version>
    <app_name>setiathome_v8</app_name>
    <plan_class>cuda60</plan_class>
    <avg_ncpus>1</avg_ncpus>
    <ngpus>1</ngpus>
    <cmdline></cmdline>
  </app_version>
</app_config>

Your GT 710 has 192 CUDA cores and I have a Nvidia Jetson Nano SBC running a Maxwell gpu that only has 128 CUDA cores. It also is running the old zi3v code branch that CyborgSam and I have wrangled into working on the ARM64 platform. This is it here:
https://setiathome.berkeley.edu/results.php?hostid=8707387&offset=0&show_names=0&state=4&appid=

So I would think your GT 710 to be at least as fast considering it has a much more powerful cpu shoveling data into and out of the gpu and is probably clocked much higher than the SoC gpu in my Nano.

OK, that is finally looking correct. I am so sorry for missing something so simple in the copy and paste. Everything is normal and found in your Event Log startup. Now just need to get some gpu work to prove out the CUDA60 app. Hopefully it won't be long before the scheduler decides to send you some. I see the gpu request for seconds of work already. It just could be the normal scheduler filling the cpu cache first before filling the gpu cache.