Advanced search

Message boards : Server and website : The server can't(?) handle files over 500.000.000 bytes

Author Message
Profile Retvari Zoltan
Avatar
Send message
Joined: 20 Jan 09
Posts: 2334
Credit: 16,178,080,749
RAC: 104,524
Level
Trp
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 57534 - Posted: 6 Oct 2021 | 22:46:49 UTC

I have a result file e4s136_e1s570p1f505-ADRIA_AdB_KIXCMYB_HIP-1-2-RND8920_0_9 which is 519.996.884 bytes long.
The upload of this result file was stuck at 476.41 MB (96.1%) for ~5 times, but (to my surprise) it eventually succeeded.
The event log says:

Started upload of e4s136_e1s570p1f505-ADRIA_AdB_KIXCMYB_HIP-1-2-RND8920_0_9 Temporarily failed upload of e4s136_e1s570p1f505-ADRIA_AdB_KIXCMYB_HIP-1-2-RND8920_0_9:transient HTTP error
I'm aware that this could be an undocumented apache webserver limitation / bug (which couldn't be fixed by the project), or this could be another effect of the unknown DDOS prevention (which prevents us from accessing the GPUGrid website in rapid succession from the same IP address) but in this case the project should make the workunits shorter to prevent volunteers waste time / energy crunching over 12/21/52 hours in vain.
The present workunits are annoyingly long anyway.

Richard Haselgrove
Send message
Joined: 11 Jul 09
Posts: 1391
Credit: 3,479,463,183
RAC: 204,625
Level
Arg
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 57535 - Posted: 7 Oct 2021 | 7:23:50 UTC - in response to Message 57534.
Last modified: 7 Oct 2021 | 7:25:36 UTC

This is caused by an (outdated) Apache configuration.

See thread 5261 - they're the same issue - and it could easily be cured by changing the limit in the configuration.

Profile ServicEnginIC
Avatar
Send message
Joined: 24 Sep 10
Posts: 515
Credit: 2,255,036,361
RAC: 626,846
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 57895 - Posted: 27 Nov 2021 | 17:14:14 UTC - in response to Message 57534.

in this case the project should make the workunits shorter

It seems that your clear claim has been at last attended.
My first task of the new batch "_ADRIA_BanditGPCR_APJ_b0-" came out today.
It took for my overclocked GTX 1660 Ti graphics card 63368 seconds to complete.
This same graphics card was completing previous batch tasks in about 103000 seconds. So there's been a significant reduction.
I was also aware to suspend network activity when the mentioned task was next to finish.
The heaviest "_9" result file was 266,18 MB in size. This leaves a great margin for not reaching any oversize.
For the same reason, I think that a greater amount of tasks can be made simultaneously available without the risk of server's data handling become overcommitted.
I hope this results in an steadier task supply...

More details in Managing non-high-end hosts thread.

Erich56
Send message
Joined: 1 Jan 15
Posts: 858
Credit: 3,585,623,930
RAC: 422,688
Level
Arg
Scientific publications
watwatwatwatwatwatwatwatwat
Message 57897 - Posted: 27 Nov 2021 | 21:43:17 UTC - in response to Message 57895.

... This leaves a great margin for not reaching any oversize.
For the same reason, I think that a greater amount of tasks can be made simultaneously available without the risk of server's data handling become overcommitted.
I hope this results in an steadier task supply...

so what remains to get solved is that tasks can finally be crunched under Windows and Ampere cards, when cuda101. So far, this combination does not work yet.

Post to thread

Message boards : Server and website : The server can't(?) handle files over 500.000.000 bytes

//