2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1


 
Thread Tools Search this Thread
Special Forums Hardware 2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1
# 1  
Old 04-11-2018
2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1

Hey MacPro users.

I just bought a refurbished 13-Core MacPro with 64GB of RAM for a cybersecurity gaming project I'm working on. Could not wait for the new MacPro in 2019, so this will have to do:

2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1

Now, I'm thinking about which eGPU to buy.

Yes, I know it's only Thunderbolt 2 versus Thunderbolt 3, but that's OK for now.

I'm looking at a number of eGPUs and various eGPU enclosure setups.

Does anyone here have a 2013 Mac Pro with an eGPU?

Thanks!
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. OS X (Apple)

DiskSpeedTest 256GB OEM v. 960GB Transcend 855 SSD MacPro 2013, 12-Core, 64GB RAM

Before Upgrade: https://www.unix.com/members/1-albums177-picture1220.png After Upgrade: https://www.unix.com/members/1-albums177-picture1221.png (0 Replies)
Discussion started by: Neo
0 Replies

2. OS X (Apple)

12-Core MacPro (2013) kernel_task over 1200%

Yesterday someone asked me to install TeamViewer and share my Mac screen with them while on a conference call. I shut down my Mac before sleeping and woke up to some major problem with my 12-core CPU in hyperdrive, and the system activity monitor showed my Mac kernel_task was at 1,200% and the... (30 Replies)
Discussion started by: Neo
30 Replies

3. UNIX for Dummies Questions & Answers

difference between Dual-core & Core-to-duo

Can anybody tell What is the exact difference between a Dual-core processor and a Core-to-duo processor ?Advance thanks to all my friends. (1 Reply)
Discussion started by: Ajith kumar.G
1 Replies
Login or Register to Ask a Question
ReportCrash(8)						    BSD System Manager's Manual 					    ReportCrash(8)

NAME
ReportCrash -- Generates crash reports SYNOPSIS
ReportCrash DESCRIPTION
ReportCrash analyzes crashing processes and saves a crash report to disk. A crash report contains information that can help a developer diagnose the cause of a crash. ReportCrash also records the identity of the crashing process and the location of the saved crash report in the system.log and the ASL log database. ReportCrash is invoked automatically by launchd when a crash is detected. For applications and other processes running in the per-user launchd context, ReportCrash runs as a LaunchAgent and saves crash reports in the user's ~/Library/Logs/DiagnosticReports/ directory. For daemons, other processes running in the system launchd context and other privileged processes, ReportCrash runs as a LaunchDaemon and saves crash reports in the system's /Library/Logs/DiagnosticReports directory where they are only readable by admin users. If there are too many crash reports saved for a particular process, older reports will automatically be removed in order to conserve disk space. launchtl can be used to disable and re-enable crash reporting. To disable crash reporting: launchctl unload -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist To re-enable crash reporting: launchctl load -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist For application crashes (but not background process crashes) ReportCrash will display a dialog notifying the user that the application unex- pectedly quit and offering to reopen the application or send the report to Apple. For developers, the behavior of this dialog can be adjusted using /Developer/Applications/Utilities/CrashReporterPrefs.app which is installed as part of the developer tools. Crash reports which are sent to Apple are submitted anonymously by the SubmitDiagInfo process. The reports are used by Apple to improve its products. Users who need support should use http://www.apple.com/support or other authorized support channels. Developers who are ADC mem- bers should report bugs using http://bugreporter.apple.com in order to allow for two way communication between Apple and the bug reporter. More information about interpreting the contents of crash reports can be found in Technote 2123: https://developer.apple.com/library/con- tent/technotes/tn2004/tn2123.html SEE ALSO
launchd(8), launchd.plist(8), launchctl(8), spindump(8), SubmitDiagInfo(8) Mac OS June 1, 2019 Mac OS