PrimeGrid PPS (Sieve) 1.39 tasks, ALWAYS "high priority"?

[VirtualLarry]

Does anyone else have this problem, that PrimeGrid "PPS (Sieve) 1.39" tasks ALWAYS seem to be running at "high priority"? Why would they set the deadlines so short?

This is on my new AMD X6 1045T @ 3.51Ghz. Using same SSD as my Q9300 install (just moved SSD over). I don't remember these tasks always running at "high priority" on the Q9300. Is the X6 that much slower than my C2Q when it comes to these tasks? They have really high estimated completion times, but when they actually run, they take much less.

Could it simply be a mistake in the estimation?

Edit: Hmm, ran the "CPU Benchmark" manually, and estimates barely changed. Something is funny here.

 

[salvorhardin]

After a wu completes does the estimated time to completion on the other wus get adjusted? I've noticed that when I start a new project the estimated time to completion is inflated, but as I get work done the time gets adjusted downward until it's fairly accurate. This adjustment period might cause the tasks to run in high priority since boinc thinks that it might not make the deadline. You might also check your connect every x day setting. If set too high boinc believes that you won't connect to the internet until x number of days and will calculate that you won't be able to send the wu before the next time it connects to the internet.