MP redesign because
we've lost so much and gained so little (I made a bulleted list
see my post #79).
I think I made a reasonable case in post 79 that the nMP is worse than the cMP in many important ways, and not better except in very few, trivial ways. So far the only argument I've received back is someone quite literally telling me to shut up.
hey mango
i think your list in 79 is accurate.. all points true.
i'll comment on one of the items though.
- 2 CPU sockets (now only 1)
i personally agree with the designer's choice on this one.. for a number of reasons.
(a little background-- i'm doing approx 100 renders per year.. i mean, i do more than that for experimental/education or personal stuff but i put out a $et of 3-5 every 2-3 weeks.. i'd say the average time per scene is 6 hours..)
rendering is one of, if not THE most resource (cpu) hogging operation in all of 'creative pro' land..
the following is based off the above.. i realize others might have different use cases than mine and the following doesn't necessarily apply.
-----
render scenes aren't just created out of thin air.. you must first model them.. you'll notice i say i put out 1 or sometimes 2 sets per month.. well the weeks in between are spent (in part) designing and modeling the objects that will be rendered.. the majority of my time working on a computer, when i'm physically sitting there doing work, is spent modeling.. during this phase of a project, you want quick response, no beachballing, no lagging, etc.. whatever speed i might be physically capable of drawing at, i want my computer to be faster..
the best chance of getting that to happen is by using the fastest processors available.
the quads or six cores are best for these phases..
now, the reason i mentioned this part is to show, that i'm completely aware of a potential logic path to follow and arrive at "well, the solution for you would be to have 2 * 6core.. that way you get the fastest processing along with twice the amount of rendering cores."
continuing...
as an analogy, my project's steps could be likened to ,say, a custom furniture maker.. she receives an order, spends the next month making the item, then ships it to the buyer.. the first part, same with me.. some sort of client contact..
the second part, her time in the shop creating the object, can be likened to me designing/modeling an object on a computer.. this is the part where i'm working with the tools.. this is where i want solid/fast/no headaches..
now, the third part, the shipping of the object.. this can be likened to the rendering phase..
at the onset of delivery phase, her work is complete.. she doesn't have to physically work or spend too much more of her time on this project.. she's done her little celebration dance already..
she does however still have a spending choice ahead.. how fast should the item deliver vs how much money do i want to spend.
assuming she's at least moderately experienced in her profession, she has finished her work a week earlier than she promised the client they'd have it in their house.. she's not even stressing shipping since she's on schedule and has properly accounted for correct shipping times..
she's competent.. most of her projects do in fact deliver on time.. but, of course (of course!) there are those times when unforeseen circumstances arise and the piece needs to be in phoenix by tomorrow.
budget wise, she going to take a hit and must spend the additional dollars for expedited shipping..
likewise, i also run behind at times and may find myself modeling on thursday night when the images are due friday morning.. and there's still 30hrs rendering time ahead.. in these instances, i obviously need 32 cores at my disposal so the render set will finish in 6hrs instead of of 30 and i'll be able to deliver as promised in large part due to my freaking awesome, albeit incredibly expensive computer..
these number can also equate to the furniture girl's crisis.. if she needs to ship to phoenix by tomorrow morning then best case scenario is pay a crap-ton of money and put the thing on a plane, pronto.
that is her ultimate option here.. it's impossible for her to deliver any faster than 6 hrs.. and if she does actually succeed in doing so, she's just spent
at least 20x her original budget.
but people who render aren't backed against a wall like that.. we have much, (MUCH!) better options available to us during similar crisis.
places like this:
https://us.rebusfarm.net/en/
that's 3000 cpu cores available to me, at a moments notice, for around $5 per scene with a rendering time of around 30 seconds instead of my 6 budgeted hours.. including uploading the scene then downloading the finished render, let's call it 2 minutes total.. or approx 180x faster than what my computer can do it at..
one of the cost-to-performance comparisons i'm faced with when buying a computer is this..
- should i spend twice the amount of money on a 12 core computer in order to get my renders back 3 hrs quicker than the estimated 6 hrs via 12 cores?
now put that up against other options also available to me:
(and fwiw, i do use these services at times.. not always.. not mainly.. but a handful of projects during the year include outsourced rendering.)
but let's just say i outsource all of my renders in a year.. (100).. and let's say i plan to use my particular computer for 5 years (500 renders total)
via outsourcing, i will spend an additional $2500 in five years (500 renders @ $5 each) with a total amassed upload/render/download
(2 mins each) time of 16 hrs.
via 12core computer, i will spend an additional $5000 in five years (5000 more than fast quad/hex) with a total amassed rendering
(3 hours each) time of 1500 hrs. (62 days)
it's 62 days for $5000.. vs 0.6 days for $2500
i know a lot of you all love making cost comparisons around here so please, even if you think i'm full of crap about everything else, please do your cost comparison on these figures.. they're very real numbers.
(another situation and another analogy would be a mass producer of furniture and a render house.. in these scenarios, the house would be able to justify an onsite render farm with no need to outsource.. and the furniture maker could justify their own shipping fleet.. but recognize this -- even in these cases, the render house is not using a personal computer to render with.. just like the shipping dept isn't using PCs (personal cars) )
i'm trying to make the point that
wanting and/or arguing over 16 cores vs 12 cores is simply setting your sights too low.. i can't stress it enough how incredibly low you have your sights set when you compare it to the sights of apple and other computer manufactures and software designers.. hardware and software designers and manufactures have much keener vision than every spec nerd here regardless of how expert they may boast.. in their (devs etc) sights are these render farms which are 100x faster than what a 12core cpu offers.. and these computer/software combos are going to be available soon enough.. look to the future (the near future).. get out of the past. these computers are designed to give you 20,40,100x speed improvements at half the cost..
recognize.
that in less than 1/2 decade, dual cpu sockets is going to look stupid when placed alongside a hardware/software combo utilizing gpgpu.. even to you hardcore_est of hangeroners