Workshop maps and clients
Hi,
I am using workshop maps on my CSGO server. Now I wonder, does the clients/players download from Valves servers or from my server? |
Re: Workshop maps and clients
Valve servers.
|
Re: Workshop maps and clients
Steam servers, which are pretty slow if you have large maps.
|
Re: Workshop maps and clients
I don't think the actual download is slow, sometimes there is that delay when it is first checking/connecting however.
|
Re: Workshop maps and clients
Ah great. thought the client was downloading it from my server after it has downloaded it.
The "Initializing map" is a bit annoying. Could take a while on some users. |
Re: Workshop maps and clients
Quote:
|
Re: Workshop maps and clients
Quote:
If you have 1000 files to download, you need to perform 1000 requests with sv_downloadurl, this is going to take quite some time (and "overhead") with the transfer, thereby raising the time required to fetch it all. If you could direct sv_downloadurl towards a full .zip, .tar.gz, .tar.bz2, ... containing all data from your server, so each individual client would only download one file, then it would work much faster. Doing it that way could however also introduce both positive and negative side effects. |
Re: Workshop maps and clients
Quote:
Bzip is really limited, unless you make res files. Your way cant be done, maybe in a dream world, and even if you could it may reduce dload time, but still cl will have to make it complete, so you wont save time, unless there was a to make it a complete file instantly. |
Re: Workshop maps and clients
Quote:
|
Re: Workshop maps and clients
Quote:
I don't assume that you go to Kiwi or REMA 1000 to pick up your soap, then go home, and then go back to Kiwi or REMA 1000 for your food, then go home and then go back to Kiwi or REMA 1000 for your toilet paper. Or do you? That would make it three trips towards your shopping chain, and why would you do that, when you can do it all in one go? In one go, it would be faster and more time consuming for you. Currently, the fastdl system (and most likely Workshop too) works like the above. It is contacting the remote sever once per file, and as such, the result is the same as if you were going to Kiwi or REMA 1000 multiple times, rather than taking all what you want in one go. Slower speeds. In the previous post, I said "If you could direct [...]": Code:
$ head -n 2 materials.txt Code:
$ cat download_individual_materials.sh Code:
$ du -sh materials materials.tar.gz materials.tar.bz2 One big file gives 19 - 19.5 seconds of downloading. And again: I said "If you could direct [...]", as things appear right now at least, you cannot make the downloads go this way. There is a huge difference between "being capped" and "feels like it is capped", in regards to your claim about the speeds being capped. I hope this makes more sense to you. |
All times are GMT -4. The time now is 09:30. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.