this post was submitted on 06 Oct 2024
13 points (62.3% liked)
Apple
17433 readers
656 users here now
Welcome
to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!
Rules:
- No NSFW Content
- No Hate Speech or Personal Attacks
- No Ads / Spamming
Self promotion is only allowed in the pinned monthly thread
Communities of Interest:
Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple
Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode
Community banner courtesy of u/Antsomnia.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you’re transferring files over a socket (like through SMB or SFTP), the receiving end usually has a small buffer, like 64KB. It’ll just pause the stream if it’s receiving data faster than it can push it to disk and the buffer gets full. So usually a file transfer won’t use much memory.
There is some poorly written software that doesn’t do that, though. I ran into a WebDAV server that didn’t do that when I was writing my own server. That’s where you could run into out of memory errors.
That lines up with what I know about networking, but on the software side I figured it would chew through memory quick (especially because it’s encrypting it on the fly).