Closed makingglitches closed 3 years ago
Simply put this should not be happening on a connection that hits a 1mb/s speed on multiple files once they start downloading.
seriously save the lies about how its somehow beneficial to anything but these pieces of garbage to keep stealing photo sand the liek from this time period where it would be just as easy for you people to stop fucking up this time period.
anyway before i go back off to ML ville
it would be possible to mark each item in different levels of readiness for download and simply add another thread that processed items that were lacking to run alongside the one that starts the actual downloads since size updates are fucking slow as balls.
Added the same working fucking code Added another timer Stop giving my code to chomos or outright deleting it.
It takes forever to process all the HEAD requests to update the sizeonserver field of the database.
Likely the http request to grab the HEAD is slower than the GET to pull the actual media items url down.
This all being pretty amazing as this is google we're talking about and i'm not throttling these requests in this case.
Likely adding a secondary processing queue with a thread would be a nice direction to go to ensure not too many are running at once, which WILL result in google temp-throttling a free account.