3 ms·
It’s definitely not easy. In general it is very hard. Some applications have been optimized and for a few applications the fit is very natural (ie, where it is
by xadhominemx 5y ago
It’s definitely not easy. In general it is very hard. Some applications have been optimized and for a few applications the fit is very natural (ie, where it is easy to avoid single threaded bottlenecks, or where you don’t need to pass data from core to core via the cache). But for general purpose workloads, it will take a lot of optimization.
- cogman10 5y agoAgree to disagree. There's a large host of applications that can benefit from parallel processing power (think, anything that can take advantage of a GPGPU). I don't dispute that some applications are hard to parallelize. However, in my day to day work, I've found that parallel operations are often not that complicated to introduce. The bigger issue is that CPUs are now so fast I find myself blocked by IO far more often than I'm blocked by actual processing.
- Closi 5y agoFor general purpose workloads maybe, but the target-audience for the Mac Pro is really for people who are using applications that are highly multi-threaded. Just look at the use cases Apple describes the existing Mac Pro for: > From production rendering to playing hundreds of virtual instruments to simulating an iOS app on multiple devices at once, it’s exceedingly capable. > Increased speed for Logic Pro X, MATLAB, Adobe Photoshop 2020, Autodesk Maya, Wolfram Mathematica Build Time, Final Cut Pro X > Tasks like animating 3D film assets, compositing 8K scenes and building lifelike gaming environments. This is the target market - and pretty much everything listed here tends to be multi-threaded. Making multi threaded applications aren't easy, but for high performance tasks all these use-cases have to be multi-threaded where possible or they are just too slow.