>There's no easy way to daisy-chain all of the linux-capable processors in my house into a make-shift renderfarm to make up for the fact that the AI grift has made compute horrendously expensiveWhat are you nerds good for? I've got two phones, a tablet, a gaming tower, a gaming laptop, a PS3, a PS4, a Wii, a TV, two smart speakers, and a suspiciously full-featured massage gun. That's gotta add up to at least, what, a 5070?
if you could abstract away the fact that they are all different machines and make it easy for normies (who own a ton of unused tech they thought they needed at some point) that just might work
>>107808442>There's no easy way to daisy-chain all of the linux-capable processors in my house into a make-shift renderfarmThere's not?
>>107808442yes there is, you can always proxmox cluster it
BOINC with me, anons!
>>107808442Let's think about it a little.You want a bunch of different machines to contribute their processing power to a pool of resources, will probably want a queuing and management system for rendering jobs, I can guess these kinds of bottlenecks:- wire/cable throughput for networking- lack of benefit in processing gain compared to power draw and management requirements for connecting multiple low-end machines together- technical debt in translation layersI'd guess things would get exponentially slower with each type of processor you're trying to use.
>>107808734In a world where You Have No New Processors And You Must Compute, none of those things matter. This is a hardening exercise against the loss of easy access to new equipment (alongside software optimization).
>>107808763>none of those things matterThat's a pretty weird thing to respond with, there. What makes it an exercise? Loss of easy access? Are you fucking broken?
>>107808796Sorry, let me restate. You've pointed out potential drawbacks, and assume that they combine to create a lethal loss of efficacy. I'm saying that processor performance is potentially, likely, additive, even with overhead, in a properly-designed meta-system (or else render farms wouldn't exist at all).>What makes it an exercise? Loss of easy access? Are you fucking broken?You are very smart. *headpats* Ego satisfied, would you like to contribute?
Hello OP, I'm a software engineer and this seems to me like the rare idea that's so obvious in retrospect but never occurred to me. I actually think it's cool as fuck. Like, the killer execution would be to do this in such a way that you could use the resources from as many different devices as possible for different applications. The RAM benefits are definitely there -- along with hard drive.There are many ways to attack the problem but I feel like the right solution should try to allow existing software to run in executors without having to rewrite them in some special language. Like maybe you would compile a program to web assembly to run on executors that are spread across devices. I'm not too sure how output rendering should be done. Whether the network would be fast enough to stream graphics from different devices, or whether you stream meta data and render only on the client.I do think this project is interesting and viable. Honestly seems more exciting than what I'm working on at the moment.
>>107808878You're forgiven for whatever the hell you're going on about, and you do not seem to be interested in discussing requirements for a project. Skip a few steps. Go ahead with whatever social engineering required that manipulative and self-witnessing tone there.My contribution is this: small electronics can get broken down into components and those can get tested and used in other electronics. Do whatever you want with your time, you can write microcode to unify disparate CPUs, we're living in the right times for bespoke-for-everything mentalities and random schizophrenics seeing opposition in realism
>>107808942Sounds good to me. I like the idea of offloading specific applications to specific units, essentially embodying particular tasks. Though it would kind of appliance-ify software, which I suppose some wouldn't like. I think, altogether, it just annoys me that I have dozens of processors that go unused 90% of the time. It's not just about compute, it's about hopefully offloading some of the wear-and-tear on my main system. It would suck for that to fail in the middle of the Grey-Goo-ening of the component market.
>>107809209any idea how to get past the GUI part though? I feel like text-based apps are easy to do with this but offloading GUI shit is going to hurt bad. Does X server solve this problem?also, is this basically what plan 9 tried to do?
>>107809226Combo of client GUI and backtracking to CLI interfaces for things that don't need GUIs? User-friendly CLI interfaces are a lost art, but getting back to that might be helpful in more ways than one.Pie-in-the-sky, I'd also like to revisit chording for input. Also helps with my ulterior motive of prepping for a wearable computing revolution once things get a little better.I realize that I'm not being practical at all. Might actually be schizo. I don't really know what's out there for this kind of thing and wanted to see what others knew about.
>>107809008>You're forgiven for whatever the hell you're going on aboutEither you understand the subject or you don't. Rhetorical idiocy is, well.. dumb. It makes accusations of posing feel like a confession (schizophrenia, too). Just say what you mean.>small electronics can get broken down into components and those can get tested and used in other electronics.>Break down functioning units to build custom hardware that is more performant as long as you don't need an unavailable component or screw up the microsoldering or short something or-You're smart enough to understand that the point is to make do with what's on hand, yes?
>>107808442>What are you nerds good for?Nothing.Haven't you learned this by now?
>>107808442I want radical edward to sit on my face
