• he/him

I occasionally write long posts but you should assume I'm talking out of my ass until proved otherwise. I do like writing shit sometimes.  

 

50/50 chance of suit pictures end up here or on the Art Directory account. Good luck.

 

Be 18+ or be gone you kids act fuckin' weird.

 

pfp by wackyanimal


 

I tag all of my posts complaining about stuff #complaining, feel free to muffle that if you'd like a more positive cohost experience.

 


 
Art and suit stuff: @PlumPanAD

 


 
"DMs":
Feel free to message as long as you have something to talk about!


plumpan
@plumpan

So I thought about this and any "normal" way to do it wouldn't really work; overclocking is just kinda "how much did you spend" if you just go by results/raw numbers. And that's not really interesting or fun. But running benchmarks and trying to get that damn thing to POST is kinda fun, if you have any excuse to do it. My thoughts were roughly as follows:

  • You post results at stock speed and overclocked on the same system, goal is basically "how much more can you get by tweaking this thing".
  • Pictures, videos, writeups, etc, about HOW you got from A to B are highly encouraged. That's the fun part basically.
  • Either people vote on what they thought was the most impressive or it's just all for fun. I don't wanna be a judge, finding judges sounds like work.

And on the technical side:

  • Benchmarks all done in linux with stuff that can be ran on a liveboot. It's Cohost, no reason to use windows here (and simplifies setup greatly).
  • I'd probably build out a lil python script that runs the benchmarks, because that sounds fun to make.
  • Would need some tests that run faster/slower so people can pick benchmarks that don't take hours to run if they show up with some old stuff.
  • CPU stuff only for the first go around, makes it more simple.
  • LN2 explicitly banned, just in case.

Really it's just a good excuse to drag out some old computer bits and see what can be done with them. If I had to guess I'd be expecting hardware ranging from "old enough that it uses DDR3" to "old enough that it requires 32 bit linux".

Does this sound remotely interesting to anyone else? Or like a bad idea? You can tell me if it's a bad idea I don't mind.


plumpan
@plumpan

Thinking about this again, probably not before EOY.

I'm thinking it'd be best to run it for a LONG time? Like, 2-3 months? I want to balance "some kind of deadline so people are more likely to do it"1 vs "oh shit I have no time to do this"

Soliciting input on this because if I do it, I'd like there to be more than 3 people including myself who partake lol


  1. I am the kind of person that benefits from having SOME deadline. I assume I am not alone.


You must log in to comment.

in reply to @plumpan's post:

puts away my thermos this sounds fun! it’d be interesting to see the differences among a bunch of different processor generations as i imagine cohost won’t be too homogeneous with platforms.

in reply to @plumpan's post:

this sounds like a real fun idea! i've got most of a 4th gen intel i5 rig stashed away in my closet that hasn't been used in a couple years, would be cool to see how much harder I could push it now that it's no longer my daily driver PC. i don't have a case for it so i'd have to figure out some kinda test bench, it'll be janky as all hell but that just makes it more fun imo.