New Mac Pro

Post by discordance » Tue, Jun 04, 2019, 1:37 AM UTC

jrockway wrote: post #373

ken wrote: post #318

Earlier quoted context omitted.

I've been on the internet. I know people lie. The OKCupid blog found that "There are consistently 4x the number of people making $100K a year than there should be" [1]. They also lie about their height, and what they look like. What reason should I have for trusting anonymous self-reported data in a category where people are known to exaggerate? [1]: https://theblog.okcupid.com/the-big-lies-people-tell-in-onli...

Yeah, so... plenty of software engineers are making $500k a year. That is total compensation; you should expect half of that to come from non-salary things like stock options and bonuses. Maybe some people are lying, but that seems about right to me for actual senior people (leading projects, maybe managing people). My last year at Google, my W2 income was in the area of $300,000. I was a "level 5" with good performa…

Post by socialist_coder » Tue, Jun 04, 2019, 1:38 AM UTC

1over137 wrote: post #502

chaostheory wrote: post #396

Earlier quoted context omitted.

The big issue with older mac pros is for how long is it able to install the latest versions of MacOS?

macOS 10.15 drops support for the MacPro5,1 (and for no other Macs).

Post by ganoushoreilly » Tue, Jun 04, 2019, 1:42 AM UTC

liquidify wrote: post #431

Miredly wrote: post #367

Earlier quoted context omitted.

It's designed to be useful for more than one kind of "Pro". The old Mac Pro, for instance, seemed to completely forget about music studios and their professional requirements for Macs. This new machine may seem like overkill to software developers, but as an audio engineer, it's perfect. I don't even want a 1TB SSD in it, the 256 is perfect to hold the OS, a few DAWs, and all the plugins I could ever want. Everything…

256 is not enough for a serious main drive in a DAW. Sample libraries should all be on the fastest drive. There are single instruments that take up 50GB. And consider that most studios are recording in 24 or 32 bits at higher frequencies than 44.1Khz. 1TB is probably enough for a music production system although I'd personally prefer larger so that I don't have to be swapping things around all the time.

Post by [deleted] » Tue, Jun 04, 2019, 1:51 AM UTC

chx wrote: post #500

ianhowson wrote: post #268

Earlier quoted context omitted.

There are plenty of cheap NVMe SSDs that can push 3.5Gbytes/sec (Samsung 970, Adata XPG). Even with dual 10Gbe NICs, you can't match that, nor the low access times of local storage. But I do agree that SAN storage is the norm here.

We are past that now, new PCIe 4.0 SSDs just have been showcased along with the new AMD chips and they can do 5GBytes/s read and a bit above 4GB/s write (AMD is rumored to have invested in the R&D of the controller). You'd need 40 GbE to match one -- and EPYC Rome, also scheduled for this fall, will have 160 lanes allowing for dozens of them. You could very easily reach 100 GByte/s read which no network will match.

Post by opportune » Tue, Jun 04, 2019, 1:59 AM UTC

llampx wrote: post #186

duskwuff wrote: post #51

Earlier quoted context omitted.

The first step up from 256GB is 2x512GB, and there's configurations up to 2x2TB. My guess is that the 256GB configuration is meant for users that work primarily with data that's kept on network storage.

There's no professional that would buy a machine with 256GB of storage. Let's call it what it is - a throwaway configuration meant to hit a price point.