1)
Message boards :
Number crunching :
Credit Milestones
(Message 128879)
Posted 1 day ago by  Penguin
300 million!
|
2)
Message boards :
Number crunching :
Badges III
(Message 128827)
Posted 2 days ago by Penguin
Woohoo! First silver shield!
Double Silver PSA!
|
3)
Message boards :
Number crunching :
Badges III
(Message 128796)
Posted 4 days ago by Penguin
Finally...
|
4)
Message boards :
Number crunching :
Badges III
(Message 128621)
Posted 11 days ago by Penguin
Finally thanks to the new 8400 CPU.
|
5)
Message boards :
Sieving :
Invalid Command queue error?
(Message 128553)
Posted 16 days ago by Penguin
It appears that this may have been due to a physical misconfiguration. When I installed the second card, the system had two PCI power cables available, which were bundled together and had 6+2 connectors. The card required one 8-pin connector. I plugged in the 6-pin connector from one cable and the 2-pin connector from the other.
Since I fixed this, no errors.
There's still an issue with this system. The reason I am running 3 sieving reservations on each card is that I can't get the expected performance without doing that. Running one or two sieving tasks per card, I get just under 170P/day for each task. Running three per card, performance is slightly less per task, which puts it in line with expectations.
Still trying fo figure that out.
GFN 18 requires a lot more CPU power to feed faster GPUs, one instance will only at most use 1 full CPU core. If it's a windows system look in task manager and see how much CPU power the sieve program is using.
|
6)
Message boards :
Number crunching :
Credit Milestones
(Message 128389)
Posted 23 days ago by Penguin
Finally broke a quarter billion the other day! 250 million heading to 500 million next!
|
7)
Message boards :
Sieving :
Invalid Command queue error?
(Message 128387)
Posted 23 days ago by Penguin
I think you should reduce your clock and memory speeds. Those errors look like what comes up and happens when the card is pushed to it's limits. Reduce it a bit and see if the errors go away.
I learned, from Azmodes, if you get errors like that reduce clocks and memory till they go away. You can adversely increase clocks till those errors occur then reduce till they subside. We learned for sieving high clock speed is best obviously but low memory is also fine and doesn't affect sieving performance.
Will try that if needed, but I havn't overclocked these cards, and one is definitely stock clocks (the other came with the system. Also, the errors are occurring on both cards. Will at least reinstall drivers first.
It really seems to act like a memory leak -- I stopped and restarted all sieving tasks last night, and no problems so far (maybe 20-22 hours).
I figured nothing was overclocked. You've sieved more than just about everyone else here... Maybe it can't handle that many instances at once...
|
8)
Message boards :
Sieving :
RTX 2080 Sieving Performance
(Message 128369)
Posted 24 days ago by Penguin
rjs5,
That's awesome! Slightly over 1,000 P/day! At least 25% faster than a 2080.....
As Azmodes said try running two instances to get a total P/day from both together.... I'm curious if even a Skylake 7820x can't feed a 2080 Ti fully with only 1 sieve instance.
Thank you for sharing your results and taking the time to run those tests.
|
9)
Message boards :
Sieving :
Invalid Command queue error?
(Message 128274)
Posted 28 days ago by Penguin
I think you should reduce your clock and memory speeds. Those errors look like what comes up and happens when the card is pushed to it's limits. Reduce it a bit and see if the errors go away.
I learned, from Azmodes, if you get errors like that reduce clocks and memory till they go away. You can adversely increase clocks till those errors occur then reduce till they subside. We learned for sieving high clock speed is best obviously but low memory is also fine and doesn't affect sieving performance.
|
10)
Message boards :
Number crunching :
Badges III
(Message 128227)
Posted 29 days ago by Penguin
b4 its gone
|
