Hey fellow devs and tech enthusiasts! I’ve been diving deep into storage solutions for my homelab and came across the Solid State Drives (SSDs), specifically the NVMe U.3 SSD 3.84TB 2.5-inch drives. These seem like absolute beasts for high-performance workloads, but I’m curious to hear from anyone who’s actually using them.

What’s your experience with U.3 SSDs compared to traditional NVMe or SATA SSDs?

Are they worth the investment for things like Kubernetes clusters, data analytics, or even gaming servers?

Any gotchas or compatibility issues I should know about before pulling the trigger?

Also, if you’re using these in a Raspberry Pi cluster or similar setup, I’d love to hear how you’re leveraging the speed and capacity. Let’s rant about storage tech—hit me with your thoughts, tips, or even horror stories!

Shut up, spammer!

@Ragnar another one needs to bite the dust!

I am Nastya and downvoted this post because I consider it spam. Your message will be removed from this community site due too much downvotes. See my profile for more information. Read my source code mentioned on my profile to see what you did wrong. Should be no problem for a developer.

Have a nice day!

If your post is not spam, please mention @retoor.

It had me in first half, not gonna lie. @Lensflare welcome to darkrant. It's the invisible part of devrant where I roam. In these rants I do p2p conversations with people by mentioning them. Soon when snek is more finished I will invite you to take a look at it using this way. That's how I got my testers. One of them made an advanced stable diffusion bot for it using my literal 5 minute make bot tutorial but he rewrote it from python to javascript. It's that easy to make an integration. Hope to have it decent enough soon! The basics of a rocket chat app is done in hours, but then work begins: scroll down every message if you didn't scroll up yourself manually, sound notifications that only play once if you receive multiple messages at the same time, benchmarking for optional ddos attacks, channel subscribing, dm's, markdown support (enabled by default, not used that much), every language supported syntax highlighting, media embedding like yt, video / image, url preview,emoji

@retoor lol

@Lensflare 😁😁😁 I do have some ticket management going on but it's not very good. But I should write down every microchange like shift enter support, making urls click able, user search, bot api / rpc protocol because rest is for pussies. My web app doesn't deal with web sockets or requests at all. It feels like all native local data. await app.rpc.* calls the uncamelcased version (snek case) automatically defined in the server RPC class using that arguments and default parameters. await app.rpc.getMessages ([xhannel_uid]) automatically gets translated to python method RPC.get_messages(self, channel_uid, since=None) for example. It's so clean. The javascript is besides that very 90's. I dropped webcomponents for serverside rendering. Since everything is a page now, every page contains inline per page dedicated js. Ofc, there's some shared js classes like App included as well. But page specific is just inline global functions. While I'm a big fan of JS OOP tho.

Admit, this is the longest reaction by saying lol you've ever had.

@retoor true

@Lensflare and no upvote :( Booeh, not even a F for effort. Typed it on a phone. )

There you go.
F :)

@Lensflare aww, you're the best and wholesome.