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
gcore(1)						      General Commands Manual							  gcore(1)

NAME
gcore - get core images of running processes SYNOPSIS
filename] process-id... DESCRIPTION
The command creates a core image of each specified process. By default, the name of the core image file for process-id will be The process information in the core file can be obtained by using debuggers. When the command creates a core image of each specified process, the process is temporarily stopped. Further, when the creation of core image is complete, the process continues to execute. Options Creates the core file with name of the file as If multiple process-id values are specified, filename will be common for all the core image files. See the section. Operands process-id The process ID for which a core image file will be created. RETURN VALUE
Upon completion, exits with one of the following values: A core file was successfully created. An error condition was encountered. In such a case, the creation of a core file is not guaranteed. The error conditions could be because of o A nonexistent or incorrect process ID was specified. o An invalid option was specified. o The current working directory of the process or directory from which was invoked had no write permissions. o The current working directory of the process was not accessible. o The file system is full. EXAMPLES
Example 1 Dump the core image of process 1030 in the file "core.1030". Example 2 Dump the core image of the process 1030 in the file "test.1030". Example 3 Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files "core.1030", "core.1031", "core.1032", "core.1033". Example 4 Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files FILES
Core image file for process-id. (Both where is invoked and the current working directory of the process.) AUTHOR
was developed by Chris Bertin (HP). SEE ALSO
adb(1), gdb(1), kill(1), ttrace(2), a.out(4), core(4). gcore(1)