Oooooo lots of PBs! As for these short MCM units, where are they? Mine still say 5 to 6 hours. I'm sure you guys snaffle them all up so I don't get any!

The points/hour does seem to be having a weird time over the last few months. Looking at JonnieB's daily top 5000 for the team and some people have twice as many results as others but have less a lot less run time yet have more points. Comparing gordoncarruthers to peter2004 on the last team top5000 for instance here .
Note, I have nothing against these guys just using their stats as an example.

And Lucky No 7 is a live one!

Welcome to the UK Team Darkmatter.NI

					
RunTime 		0:001:13:52:56	# 587,446		
Points  		15,021	# 447,635		
Results 		70	# 392,876		
					
Devices		             1			
					
Joined WCG		06-Jun-14			

Last Active 08-Jun-14 02:17
Don't hesitate to post if you have a query or need information.
One of us will always be happy to try and help.

Currently I'm seeing 10 day deadlines on 2nd copy issues for P/Ver WUs for FA@H & CEP2. Can someone supplythe corresponding details for MCM1?

I ask because the standard is supposed to be 3 days per the FAQ. I'm not aware of any formal announcement of the change?

Firstly, welcome to the team, it's good to see new blood willing to help out!

When you finish a work-unit, your client will automatically upload the results to the work-servers and mark it as completed, but you still need to report it in order for the servers to do the relevant work to confirm the result is valid. I tend to put in a scheduled task to automatically report any completed units (and download any new ones) on my servers - how often that task runs depends on the speed of the server (anything from hourly up to every six hours for the slower servers I run).

In your client, you should have an Update button on the Projects tab - that will register any "Ready to Report" units as fully completed, and give you the runtime/points/result to add to your total once the server does its updates twice a day.

There are currently no GPU-enabled tasks for WCG, so that setting being enabled or disabled should make absolutely no difference if you're only working on WCG work-units. Of course, this will be different if you're doing GPU-crunching for other projects (GPUGrid, etc) other than WCG. The time-difference will just be down to normal variance in work-units, as coincidental as it sounds about them taking twice as long when it's enabled.

If you're worried, leave it disabled until there's news on the forums about a GPU-enabled project - there's enough of us in here, waiting for that day, so I'm sure it'll be regularly talked about when it happens.

Nice CPU, that should be churning through the work-units quite nicely...