119 karma · joined March 13, 2017
And I also had an older lg 4k monitor that bricked itself after a power outage, which is apparently a known eeprom issue.
Now this. No more LG for me.
I’m not sure if it was actually a well thought out idea, since it’s not like fb has a lack of servers or bandwidth, but I didn’t work on it, so I don’t want to throw too much shade at it.
I’m not even using a 800G cable since they are expensive and I don’t think I need the bandwidth, opting for 400G instead. This just needs a config change for the number of Ethernet links it uses internally. (Apparently these cables are just many 200G links put together.)
My setup has 4090 handling attention while TT accelerators handles MLP. With just a 4090 you can have CPU handle the MLP layers and use a MoE model, assuming sufficiently powerful cpu. I tried that setup with minimax 2.5 before, and was able to eke out around 10 to 15 tps (albeit with a 7965wx cpu)
The entire stack (minus some binary blobs in firmware) is open source, so if you have the time and persistence you can get whatever you want done.
A few community members have been working on support with llamacpp, where we can have supported operations offloaded to the TT cards, while having unsupported ops running on GPU or CPU. Llamacpp is pretty good at that. The existing kernels could definitely be better, and I’ll try my hand at writing some kernels some time.
The main issue is the immature software, and somewhat baroque way of writing kernels. Please, buy one and join us.
Would like to see the perf of their setup with and without mtp and ngram speculative decoding though, as well as parallel decode performance (once llamacpp mtp plays well with multiple slots).
Being in California electricity alone puts this non-competitive with just paying a cloud though.
AMD threadripper pro 9965WX, 256gb ddr5 5600, rtx 4090.
I also tried fedora coreos for a vm + container host, but found the recommended method to configure the system with ignition files and one shot systemd units to be too involved for making a one off system, and it’s probably better for a cloud deployment with many identical nodes.
This one seems to be directly related to the webrecorder project which seems like a pretty full featured warc recorder.