Archived threads in /g/ - Technology - 4072. page

File: Clipboard-2.jpg (252KB, 1920x1084px) Image search: [Google]

252KB, 1920x1084px

Something is wrong with the way the games are utilizing the cores which seems to confirm it's an issue with game code or something in the driver/BIOS/Windows causing this.

File: speccy.jpg (58KB, 660x525px) Image search: [Google]

58KB, 660x525px

Despite Ryzen meeting everything the industry asked for (competitive IPC, more mainstream cores, ECC support, and thermal/power efficiency), it is being deemed a failure because a Quadcore at 5GHz scores slightly higher at an unplayable resolution on video games.

This cultist bullshit is the reason we have been stuck with 4 core CPUs for a decade. Intel jackoffs are not only pitting two seperate class CPUs together, but they are doing that on top of using single threaded, horribly optimized applications.

Newsflash: using a terrible game such as FO4 as a metric for a CPUs performance should not be encouraged. It is 2017, if something cannot utilize multiple threads, it should be completely thrown out of any review. As long as we keep caring about Single Threaded performance, the longer we will have single threaded applications.

Comparing the R7 chips to X99 CPUs don't even make sense. X99 doesn't support ECC, and they run at the highest TDP Intel offers. Pit it against an 8C 16T Xeon, on workloads the CPU was made for.

If you want to test stupid shit like CS: GO, wait for the damn 4C8T R3 chips, not the goddamn adult CPUs. Then you can't fucking get your holy single thread performance by OC'ing a pathetic core config to ridiculous clockspeeds.

If you cannot understand why you are fucking retarded for thinking a 7700K is somehow better than a R7 1700, you are fundamentally missing the whole picture.

Pic semi related: Shows I'm not a diehard AMD fan, I just prefer to have technology advance over brand loyalty

File: yuki_k&r.png (350KB, 500x492px) Image search: [Google]

350KB, 500x492px

What are you working on, /g/?

Old thread: >>59209636

File: sdasdffdsafsdfasdafsd.png (8KB, 140x167px) Image search: [Google]

8KB, 140x167px

So, making a cross compiler on linux for windows. Binutils was fine compiling and configuring for x86_64-pe, but gcc doesn't like that, and claims it's not supported.

I'm literally just using the configure script on both of these, then running make as per the OSDev Wiki's instruction.

Anyone know what I'm doing wrong, aside from
>developing for windows

File: file.png (607KB, 800x500px) Image search: [Google]

607KB, 800x500px

> b-b-but Vulkan/Mantle/nuOpenGL/nuDirect3D will make my games or desktop applications run even faster with my 32core/64thread CPU
In most cases they make the CPUs even MORE irrelevant.
Read the basic descriptions about Vulkan on that:
> Reduced driver overhead, reducing CPU workloads.
> Reduced load on CPUs through the use of batching, leaving the CPU free to do more computation or rendering than otherwise.
> Better scaling on multi-core CPUs. Direct3D 11 and OpenGL 4 were initially designed for use with single-core CPUs and only received augmentation to be executed on multi-cores. Even when application developers use the augmentations, the API regularly do not scale well on multi-cores.
Out of 3 advantages, 2 of them REDUCE CPU load even further, and the third is usually not even needed to begin with since the GPU has been already bottlenecked.
So in order for Vulkan to make multicore CPUs more relevant, they must do EVEN MORE parallel stuff ALREADY *(and in most cases they do almost nothing before Vulkan appeared), or it's used on software that does NOT bottleneck a GPU at all which is kinda unrealistic for most gaming scenarios and a lot of non-gaming also.

File: unnamed (2).png (33KB, 281x524px) Image search: [Google]

33KB, 281x524px

Is earning money off this just a meme?

File: MegaUNLIMITED[1].jpg (80KB, 1280x720px) Image search: [Google]

80KB, 1280x720px

Does mega.nz actually work?

File: ayylmao.jpg (295KB, 914x1080px) Image search: [Google]

295KB, 914x1080px

Since everybody is shitting this board up with ryzen/amd let me ask this question-
Did i won silicon lottery or is jewtel on suicide watch?

File: 1458397321854.jpg (37KB, 500x401px) Image search: [Google]

37KB, 500x401px

>walk into comp sci class
>there's a kid that always seemed very /g/ like to me
>seems to be balding (younger than fucking 22 )
>had a Thinkpad
>SEEMED autistic
at this point i just start to go and put my stuff down when a chick asks him what his hat says and uh
>he was wearing a fucking top gun hat
>makes a smug smile face almost as if he was copying the smug chinese cartoons that get posted here
>he was running some autismo Linux distro
>he's pretty much autistic
that kid was falling for so many fucking memes all at once it was unbelievable. If you're reading this autismo please take a look at pic related, and throw away the shit hat
I really hope the rest of you aren't such fags

File: 2017-03-03_1600x900.png (278KB, 1600x900px) Image search: [Google]

278KB, 1600x900px

Browser ricing thread, show us what you got

File: file.png (44KB, 638x468px) Image search: [Google]

44KB, 638x468px

I wonder if people have ever tried to code something in low level OpenGL or Direct3D. Those subsystems do most of the parallelism on the GPU level, don't work well with multithreading on the CPU level/they often work even faster if a single thread is feeding them instructions, and in many cases you can make it much worse by multithreading them. In many game genres it's simply bad design to not go largely single threaded when all you do is feed extremely simple stuff to an extremely paralleled GPU pipeline.
People should shake their heads when others suggest that games can become a lot more multithreaded on the CPU level since in most cases the most you can subthread is something like a sound engine that won't be more than 2% of your load, the genre might not even need AI and similarly for other game logic, and a lot of that stuff also move into GPUs' parallelism to begin with.
PS. Some benchmark reviewers are so clueless that they bottleneck their GPUs and then pretend that they do a CPU test. The entire point is to test the CPU bottlenecks when you test CPUs. If you don't, you practically do motherboard testing.

File: Picture1.jpg (117KB, 800x527px) Image search: [Google]

117KB, 800x527px

Would it be a waste of time to learn programming/coding skills if I have no interest in pursuing it as a career? Could it be useful just to become more tech-savvy? Is there such a thing as "hobby projects" in programming or is it all done as work?

Apologies in advance if these questions are retarded/don't deserve their own thread.

File: amd king.png (1MB, 1430x719px) Image search: [Google]

1MB, 1430x719px

>buy intel 7600k
>temps are shit
>have to jew out $75 on a good aftermarket cooler
>temps still shit
>intel jewed out on the TIM and I have to delid it
>have to spend $20 on an aftermarket delidding kit
>oh and $7.80 on a tube of replacement TIM, plus tip :^)
>have to spend $50 on a vice grip to hold cpu
>finally get all my equipment
>delid CPU and install into motherboard
>CPU bends and breaks because aftermarket coolermaster giganigga 9000 BBC edition was too heavy
>intel cheaped out on the substrate too

>mfw i should have just bought a ryzen which comes with a soldered IHS, THICC substrate, wraith cooler, and jim keller BWC technology

File: 7814.png.jpg (44KB, 530x345px) Image search: [Google]

44KB, 530x345px

So I somehow got this gig teaching middle schoolers to program, what the fuck should I do? Scratch looks like a good example but is it enough?

File: 1488491035624.png (96KB, 1920x1012px) Image search: [Google]

96KB, 1920x1012px

C apologists are NSA shills plain and simple. Rust makes it harder to produce vulnerable programs as it actually implements safety precautions like Bounds checking, dangling pointer prevention, data race prevention, lifetimes etc. This is against the interest of the NSA and so they are shilling C so that people continue to produce exploit prone, unsafe and vulnerable programs.

Ignore the NSA/C shills. Programming in C should be banned and outlawed.
Say no to security exploits, say no to the NSA. Your data and your privacy is worth preserving.