Theory crafting a system for 1000 simultaneous micro SD card ingests

I hope they have a robot for physically handeling the SD card insertions and retrieval. Even then, lets say you can load or swap 1 card per second, by the time you are dealing with the 200th card, would the first one not already be ingested?<p>Seems like more of a scale out than a scale up problem, with a view on the <i>whole</i> operation from recording footage down to final archive to tackle the real bottleneck.

I know it sounds boring, but did anyone suggest a second computer if this is an actual problem and not just a for fun challenge?

The physical interface itself is going to be a big deal, people are going to be just swapping cards constantly and you&#x27;ll need multiple people just doing this. Status of read is a big part of this as well so some amount of custom LEDs and such for status of ingress will be required. What a horrible job being in a room with 100s of thousands of SD cards just feeding them into slots and then into an empty bin!<p>Its possible from a PCI-E bandwidth point of view but its going to require some seriously specialist USB interfaces. I am tempted by the same solution others suggest, smaller amounts per machine less expensive and extreme solutions into normal switches and then out across fibre.<p>What a crazy thing to be doing, the mad situations companies get themselves into when they should just have networked cameras and VPNs or at the very least distributed ingress machines!

Such a nerd bait request. I’m like “wait, how long between downloads of cards do you need? How many people will be placing these cards in? How will you know when one is downloaded??”<p>Only reading the comments did I think “Wait, who needs this and why?” I like the Mr. Beast angle - it’s fun to think about if nothing else.

One use case is to mount 360 cams on a bunch of motorcycles (fleet) and do a google streetview equivalent. You build a city level streetview pretty quickly.<p>I think at that point you&#x27;d just need to do 1 pc every 200 readers and pull the videos to a local server for processing. There&#x27;s no magic here, just work.

They should simply outsource it to lowest bidder, preferably on a rando internet forum.

I&#x27;d go in a completely different direction from this.<p>I&#x27;m assuming the SD cards come from a fleet of dashcams or similar, and that the driver is responsible for turning in their card at the end of a run or whatever.<p>I&#x27;d deploy a fleet of tiny WiFi card readers. Just an ESP32 and a card slot. Each individual unit is not fast, but if you have a few dozen units running at once you could easily saturate the dedicated ingest WiFi network at each hub location. The readers are dirt cheap and the only supporting infrastructure required is WiFi and a bunch of 5v power adapters.<p>You&#x27;d have a rack of these guys next to the key locker or timeclock. Pick up your keys and a blank card, drop off your keys and card at the end of the shift. Could even get extra fancy and use LEDs to indicate which card is yours for the day, or flip on an error light when the card is worn out.<p>You probably don&#x27;t need <i>each</i> video to transfer as fast as possible, more likely you just want maximum overall throughput. So just build a bunch of very cheap and slow nodes. On aggregate you should get decent performance.

I was not expecting that thread to go in that direction. At first my nerd brain kicked in and I started doing the PCIe napkin math - but then I got to the post asking &quot;why?&quot; and found myself asking the same question.<p>I am also a bit perplexed on why they&#x27;d need to ingest 1,000 micro-SD cards at once. If they are such a large org, why not investigate alternative solutions?

At that scale, wouldn&#x27;t it make sense to just have raw block i&#x2F;o copies being done to a disk image, and then mount the image onboard to do the actual data transfers?<p>Seems to me a majority of the overhead with 1000 SD cards is in the filesystem translation layer, multiplied by the USB contention dealing with so many devices.<p>So if it were me, I&#x27;d have a big fat, fast mounted filesystem whose purpose is only to serve as a dd destination, get the dd done as quickly as possible with system bus buffer sizes, and then do the data transfer &#x27;offline&#x27; once the SD has been mirrored...

So, the 1000 card problem is pretty easy. What matters is how much is on each card, and how long the DL window is.<p>For instance, if you can spend 2 hours downloading each card, (SPI to an esp32 can do about 32GB an hour) so you could Download 64GB in 2 hours via ESP32 boards with SPI uSD slots, pushed onto your server over wifi6.<p>If that’s enough, that’s a simple solution. If you need more than 32GB an hour per card, I’ve seen some adapters that hold 10? uSD cards and connect over SATA, so that might get you a better way into the bus than typical USB?

There is only one scenario that remotely makes sense for why this would be even necessary and that&#x27;s fleet vehicles with dash cams. Even in that case, there are way better approaches because there are dashcams designed for fleet usage that upload to central servers over WiFi.<p>Basically this scenario only makes sense if there is something horribly wrong elsewhere to the point that the only reasonable thing to do is fix things to involve a network, not to try to figure out how to scale a sneakernet operation.

&quot;i can provide more details if needed but some things i am under an NDA so i may not be able to answer specifics&quot;<p>LOL why are these people helping this guy for free?