Thank you for trying to understand the problem.
I have about 40,000 json files (~280 MB) + 5,000 html files (~5 MB) = ~300 MB
Is 50,000 static files a lot? What is the limit on the number of files?
There us no specific limit on number of files, but higher numbers use more memory during our upload process. We have many sites with that many (~45k) files, but 500k would be more than I’d expect to “just work”. Thanks for those stats, they’ll inform that bug report.
As far as things you could try to unblock yourself today, since we won’t be able to investigate more deeply in the immediate future: you might consider trying to deploy subsets on separate sites and stitch them together as described here (you’ll use the same repo, but you can proxy to the second site using the pattern described there: [Support Guide] Can I deploy multiple repositories in a single site?). Suggestion: before trying to set up proxying, try simple deploys of half of your content and see if the deploys complete, since that’s a prerequisite for it being worth your time to try that sharding.
Hello. I think I’m going beyond a certain limit. Could you say what are the service limits?
5:46:45 PM: Skipping functions preparation step: no functions directory set
5:46:45 PM: Caching artifacts
5:46:45 PM: Started saving node modules
5:46:45 PM: Finished saving node modules
5:46:45 PM: Started saving build plugins
5:46:45 PM: Finished saving build plugins
5:46:45 PM: Started saving pip cache
5:46:52 PM: Finished saving pip cache
5:46:52 PM: Started saving emacs cask dependencies
5:46:52 PM: Finished saving emacs cask dependencies
5:46:52 PM: Started saving maven dependencies
5:46:52 PM: Finished saving maven dependencies
5:46:52 PM: Started saving boot dependencies
5:46:52 PM: Finished saving boot dependencies
5:46:52 PM: Started saving go dependencies
5:46:52 PM: Finished saving go dependencies
5:46:52 PM: Build script success
5:46:52 PM: Starting to deploy site from 'public'
5:47:57 PM: Creating deploy tree asynchronously
5:48:21 PM: Creating deploy upload records
5:48:28 PM: Failing build: Failed to deploy site
5:48:28 PM: Failed during stage 'deploying site': Failed to execute deploy: Put https://api.netlify.com/api/v1/sites/9f9381ec-9aa8-41cc-ae47-c0fc3f34aa4d/deploys/5ec692c5e3af1b017423b796: context deadline exceeded
5:48:28 PM: Finished processing build request in 8m20.956564722s
Hi, @pleer-video, there is a fifteen minute limit on builds and an additional fifteen minutes permitted for any post processing needed (if any).
Would you please send us a link to this deploy? (Or send us the “deploy id” is the last path segment of the URL when viewing the deploy detail/logs in our web app?)
Also, do you know approximately how many files there were in that site build?
Additional questions are always welcome and we’ll be happy to research the deploy once we know which one it is. 
Thanks for your reply.
5:48:28 PM: Failed during stage ‘deploying site’: Failed to execute deploy: Put https://api.netlify.com/api/v1/sites/9f9381ec-9aa8-41cc-ae47-c0fc3f34aa4d/deploys/5ec692c5e3af1b017423b796: context deadline exceeded
Is this not a link?
Thanks, that was what we were looking for around links. After discussion with our backend team, we probably won’t be able to support deploying that site on our system at present. Sorry I don’t have better news for you today! Should we get the bug we have opened on the problem fixed, we will absolutely notify you so you can confirm our fix and use our platform.