Tell me one good reason why you don't have at least 12 cores.
I'll do you better and give you two reasons.
1. Can't afford
2. Don't need
tell me one good reason why you're using unity.
KDE, gnome, Xfce - the options are so much better.
>>51675839
Watching porn and shitposting doesn't require 12 cores.
>>51675861
>can't afford it
>makes up reasons to not have at least 12 cores
Those grapes sure are sour to you, huh?
>>51675864
>anything mainstream is bad and I only like oldschool things because linux is all about oldschool things
Render something with POV-Ray in 1080p with the+A0.0, +Q12commands and post PNG fagit.
>>51675839
99% change that's either 6 cores with hyperthreading or 12 AMD cores which is like 4 intel cores.
1) Im on a chromebook
2) All i do is shitpost all day
3) ChromeOS is effecient enough where a 2 core 2.6ghz celeron and 2gb of ram does just about anything i need it to do
4) I dont game
5) Higher core counts are still too pricy for what they give you in performance
>>51675989
What if it's 12 individual pentium 4 cpus clustered together?
>>51676012
Then they aren't sharing memory so that doesn't count.
>>51675989
i7 5930k
>>51676029
Which is 6 cores.
So tell me one good reason why you don't have at least 12 cores.
>>51676036
logical cores handle 12 threads which is as good as 12 physical cores for the job of running 12 cpu-taxing jobs at the same time
>>51676066
I can't tell if you're baiting or have no idea what hyperthreading does.
>>Has 6 cores
>>makes a thread about having at least 12
>>51675976
this.
>>51676084
>>51676066
>logical cores handle 12 threads which is as good as 12 physical cores
Nope.
The "logical cores" are only for the benefit of the operating system. Hyperthreading only allows CERTAIN COMBINATIONS OF INSTRUCTIONS to be executed simultaneously. It's highly variable.
Hyperthreading is nothing like having 2x cores. You just get better performance in certain situations.
>>51675839
Money
The fact that we usually need more than two cores for day to day PC usage is ridiculous in its self.
We should teach devs to be less shitty with their code then just make CPUs more powerful.
>>51676183
What about ray tracing? Would it make any difference in rendering time between 12 threads and 6 threads on a 6 core i7?
muh cores: the thread
>>51676227
you still have 6 cores faggit
>>51675976
Pic related took me 5 minutes to render on my quad core A10-4600M APU @ 2.3 GHz.
Portability and performance.
>>51676183
python multiprocessing async jobs take advantage of logical cores
>>51676235
You do realize it's the only way we will ever reach real time ray tracing right? Maybe in 2030 when 128 core x86 cpus are around we'll be able to render real time ray tracing in 4K res.
>>51676227
>What about ray tracing?
Like I said, certain operations can be executed simultaneously. It's obviously a statistical problem. With what frequency to these sorts of operations come up in the pipeline? No idea.
>>51676292
How's that? How is the Python execution engine in any way able to "take advantage" of logical cores?
I think what's actually happening is that it's multithreaded. Meaning the operating system assigns threads to different logical cores. So that doesn't really mean anything about Python somehow "taking advantage of logical cores", it just means Python does some kind of multithreading logic when batching async operations.
>>51675839
Because I have a Pentium 4 from 11 years ago. The motherboard doesn't even support core2duos' so I can't even update because motherboard + CPU + RAM (current mobo has DDR1) gets a bit too costly for me.
>tfw mobo doesn't even have PCIe slots and just a couple of PCI slots so can't even buy a GPU and enjoy games
>>51676332
Yep that's what I meant. I'm mainly a python guy so that's what came to mind, but async jobs in general do take advantage of idle logical cores, so there's definitely an advantage there against a regular single logical core- single physical core architecture.
Most of my programming benefits from multithreaded work and runs up all cpu cores to the max since it's all mostly asynchronous.
>>51675839
Because I have zero coars thanks to my computer dying. :(
I'll build one sometime.
(Currently posting from a hackintosh I built for my parents for Christmas. Works quite well. OSX interface is shit.)
>>51676260
Dam, why don't video games look like this?
>>51676362
>async jobs in general do take advantage of idle logical cores
Sigh. No they don't. Stop talking.
Or better yet, learn how to directly do multithreading in a real language instead of just waving your hands and misusing terminology.
>there's definitely an advantage there against a regular single logical core- single physical core architecture.
Like I said, it's a statistical thing.
>>51676615
Do you even know how to code? Most scientific programming takes place in Python.
>>51675839
I don't encode video
>>51676260
>>51676455
5 minute to render 25 pawns...
That's why, vidya needs realtime
>>51675839
>ubuntu
>unity
>chrome
>steam
>skype
>>51675839
I picked up two six core CPUs for my dual socket server but I can't seem to find the BIOS update I need to make them work
>>51676455
Mostly because it takes too long to ray trace things. Currently even the i7-5960x can't ray trace in real time. GPUs are also dogshit for ray tracing as well so they have to use other methods to make games look realistic.
We might see affordable CPUs become powerful enough to ray trace in real time in the next 10-20 years though.
Pic related took me 13 minutes to render.
>>51675839
Why are those shilling thread even allowed ?
>>51676335
pix of pc plz
>>51677814
Here
>>51677915
craigslist is your friend.
>>51675839
I refuse to pay intel jews
>>51677977
You don't need Intel for a 12 core system
>>51676335
The least you can do is get yourself a cheap-ass Thinkpad, even if it's just a Core 2 Duo one. Anything to escape Netburst hell.
