Seti for BOINC was comparable speed-wise to v3.08 "classic", meaning roughtly 10% slower than v3.03. But the new v4.05 (win-only) is for some reason even slower. Most probable reason is some debug-code was left on, or code-changes...
This really doesn't mean much, since the crediting is based on crunch-time, and even with the slower v4.05 BOINC is more efficient than "classic" since only sends the same wu to 3 users normally and not 7+ as "classic" is doing.
As for no credit, the validator has been back-logged for a long time, and seems to have been turned off the last couple of days meaning no credit to anyone. Also, there's no credit before 2 other users also has crunched the same wu, so even if everything works it can take upto 14 days before all has returned the result, even longer time if someone reset/detach/miss deadline.
Also, uploading results is a 2-step-process, there the result-file is normally immediately uploaded then finished crunching, but the servers doesn't know of this before the result is Reported. Results is reported next time you're connecting to the scheduling-server, either due to asking for more work, nearly reached deadline, or if manually "update project".
The preference "Connect to network about every x days" will normally cache between x & 2x days of work, so because of the 14-day-deadline don't set x higher than 7. Also, since in v4.05 the wu takes longer than expected to crunch, I'll recommend to not set this higher than 5 for the moment.
Any upload-errors or other problems can also be the reason for no crediting, this will show up under Messages-tab in the gui, or stdout.* sterr.* in BOINC-directory, but unfortunately service-install haven't currently any logging.
A last reason can be, if you're overclocking, you're overclocked too much so you're only returning garbage, and BOINC doesn't give credit for this garbage...
edit - If you're using BoincView or another similar monitoring-tool, you'll get the message-info even if installed as service.
😎 More info on boincview,
here
