Reply With QuoteIt happens infrequently, nothing will be lost and it'll be back up soon I think. The clients just hold their blocks and then submit them once they see the server again.
Nothing to worry about
Bok
http://seventeenorbust.com/stats/use...ml?userID=7660
I suddenly dropped to 0.
Then I saw that Free-DC dropped to 0 as well.
Stats issue? Can anyone confirm?
It happens infrequently, nothing will be lost and it'll be back up soon I think. The clients just hold their blocks and then submit them once they see the server again.
Nothing to worry about
Bok
Great thanks.
I thought I have brought down the server.
Just kidding.
to NOT transmit intermediate blocks as you will lose shedloads of cycles.
I am considering doing that.
My fastest clients are sending 1500 blocks a day each the slowest ones about a 1000.
Ads up to a lot of connections to the SOB server every day and waisted crunching time.
Wonder if there is some way to send say 100 blocks at a time automatically instead of 1
Keeps the production rate graphs smooth though.
So if we do that, how will that work? It will transmit all once the test is completely done?Originally Posted by Fozzie
I think that would be best if I were to fully deploy on SoB because it'll increase my network traffic significantly.
It only takes a second to communicate with the Server. Not much time lost, nearly nothing trasmitted.
Yes, only when the whole WU is completed, will it reach out to the Server.
If you want to do that way, in that .reg example I gave you
Change this: "transmit"=dword:00000001
to this: "transmit"=dword:00000000
normally it only takes amtter of a second but when there is the server side glitch like yesterday then that becomes 5 and sometime nearly 10 seconds until it times out.
It depends on whether you have some really quick machines on it or not.
Posting Permissions
