5 ms·
ChatGPT and Wolfram Alpha confirmed to me that it's about 37 days, which is 888 hours, not 88 :) Wolfram Alpha: https://www.wolframalpha.com/input?i=400tb+at+1
by Timothee 2y ago
ChatGPT and Wolfram Alpha confirmed to me that it's about 37 days, which is 888 hours, not 88 :)
Wolfram Alpha: https://www.wolframalpha.com/input?i=400tb+at+1gbps https://www.wolframalpha.com/input?i=400tb+at+1gbps
ChatGPT: https://chatgpt.com/share/4ddd464a-dabd-4c12-9cc4-e8271a51a671 https://chatgpt.com/share/4ddd464a-dabd-4c12-9cc4-e8271a51a6...
(ChatGPT did a great job at breaking down the problem)
- cassianoleal 2y agoSo did your sibling comments and I imagine anyone with very basic maths skills could. And most likely burning a lot less carbon than ChatGPT.
- dsjoerg 2y ago[flagged]
- cassianoleal 2y ago> the AI you used to write this I don't follow. Are you suggesting I'm an AI? Or that my answer was copy-pasted from an AI? > HN is kinda asynchronous Or that HN runs an AI to serve the website?
- netsharc 2y agoExcept everyone is forgetting the TCP/IP overhead. I also asked ChatGPT, and 400TB of data creates a 10.7TB overhead, which adds ~5 days...
- dark-star 2y agoif you had done the math yourself you would have arrived at a different number....
- netsharc 2y agoHow so, care to educate the lazy? It's all theoretical anyway, if it's 400TB split into individual files, and I'm using millions of HTTPS GET's, that's also overhead... Gotta love nerds spending their Saturday (nights) arguing about some simple maths...