Sending results take over 30 minutes

[yahavbr]

Hi, I only recently noticed that sending the results is taking more than 30 minutes to complete.. is this normal?

If yes, how so? Is the client sending huge amounts of data?

If not, what can I do to improve it?

Thanks!

[Tobit]

Very normal especially if you are using the SMP client. You can expect your uploads to be at least 50 MB in size with some averaging even larger than this.

[gwildperson]

The amount of data being uploaded depends on the particular project, but yes, some results are quite large. (I've seen a lot more complaints that FAH hogs the bandwidth than requests to make it upload faster.) The data is already compressed, so there's probably nothing that can be done unless you want to order a faster connection from your ISP.

[yahavbr]

Thanks for the fast response(s) this is exactly what I wanted to know and I'm fine with this.

[lanbrown]

Very normal especially if you are using the SMP client. You can expect your uploads to be at least 50 MB in size with some averaging even larger than this.

The SMP results are in various sizes. The smallest is ~4MB, then ~20MB, ~43MB, ~63MB and then over 100MB. Currently the majority of the WU results are the 4 and 20MB variety.

[yahavbr]

Very normal especially if you are using the SMP client. You can expect your uploads to be at least 50 MB in size with some averaging even larger than this.

The SMP results are in various sizes. The smallest is ~4MB, then ~20MB, ~43MB, ~63MB and then over 100MB. Currently the majority of the WU results are the 4 and 20MB variety.

How can I see the size? Does the console show this? Or can I just see size of specific file or folder?

[lanbrown]

The console shows it. I highlighted the important bits. The code tag doesn't support the bold.
Example:
[13:33:55] Completed 500000 out of 500000 steps (100%)
[13:33:56] DynamicWrapper: Finished Work Unit: sleep=10000
[13:34:06]
[13:34:06] Finished Work Unit:
[13:34:06] - Reading up to 3698352 from "work/wudata_02.trr": Read 3698352
[13:34:06] trr file hash check passed.
[13:34:06] edr file hash check passed.
[13:34:06] logfile size: 56934
[13:34:06] Leaving Run
[13:34:10] - Writing 3790438 bytes of core data to disk...
[13:34:11] ... Done.
[13:34:11] - Shutting down core
[13:34:11]
[13:34:11] Folding@home Core Shutdown: FINISHED_UNIT
[13:34:11] CoreStatus = 64 (100)
[13:34:11] Unit 2 finished with 92 percent of time to deadline remaining.
[13:34:11] Updated performance fraction: 0.923717
[13:34:11] Sending work to server
[13:34:11] Project: 6070 (Run 1, Clone 64, Gen 8)
[13:34:11] + Attempting to send results [September 15 13:34:11 UTC]
[13:34:11] - Reading file work/wuresults_02.dat from core
[13:34:11] (Read 3790438 bytes from disk)
[13:34:11] Connecting to http://171.64.65.54:8080/
[13:34:13] Posted data.
[13:34:14] Initial: 0000; - Uploaded at ~1234 kB/s
[13:34:14] - Averaged speed for that direction ~1238 kB/s
[13:34:14] + Results successfully sent
[13:34:14] Thank you for your contribution to Folding@Home

[yahavbr]

I don't have so many details when sending results, only this:
[09:55:51] + Attempting to send results [September 15 09:55:51 UTC]
[10:33:02] + Results successfully sent
[10:33:02] Thank you for your contribution to Folding@Home.

However I do see this before the sending:
[09:55:44] Leaving Run
[09:55:47] - Writing 43656405 bytes of core data to disk...
[09:55:47] ... Done.
[09:55:49] - Shutting down core
So it means 40 MB of data which indeed takes over 30 minutes to upload.

Thanks!

[Tobit]

I don't have so many details when sending results, only this:

Enable the -verbosity 9 flag in your client command line options and you will get the additional log file detail.

[yahavbr]

I don't have so many details when sending results, only this:

Enable the -verbosity 9 flag in your client command line options and you will get the additional log file detail.

Just so I'm 100% sure, the command should now be: "[path]\Folding@home-Win32-x86.exe" -smp 8 -verbosity 9 ?

[PantherX]

Yes, that is correct. Also when the Client is uploading the data, you navigate to the installation folder and go to Work folder and there you will see wuresult_XX so you can check out its size.

The time take to upload the wuresult depends on the size and upload speed. What is yours? For me, it takes 2.5 hours to upload ~100 MB (bigadv WU) at ~10 KB/s

[yahavbr]

Yes, that is correct. Also when the Client is uploading the data, you navigate to the installation folder and go to Work folder and there you will see wuresult_XX so you can check out its size.

The time take to upload the wuresult depends on the size and upload speed. What is yours? For me, it takes 2.5 hours to upload ~100 MB (bigadv WU) at ~10 KB/s

Cheers, changed the batch file and will check it out after the next restart.

15 - 20 KB/s upload speed here, so the half hour is normal.

[lanbrown]

Yes, that is correct. Also when the Client is uploading the data, you navigate to the installation folder and go to Work folder and there you will see wuresult_XX so you can check out its size.

The time take to upload the wuresult depends on the size and upload speed. What is yours? For me, it takes 2.5 hours to upload ~100 MB (bigadv WU) at ~10 KB/s

Cheers, changed the batch file and will check it out after the next restart.

15 - 20 KB/s upload speed here, so the half hour is normal.

I'm spoiled then, as fast as Standford (and TCP settings) can take it, it goes.