With over 17 years of IT hardware supply chain resources


Server Q&A

My suggestion is to get a superpower system. As others have pointed out:

Xeon’s use of ECC should help novice programmers learn Pointers with fewer system crashes. Well, not really. I was a bit rotten and lost data due to bit rot. In my 20-year history of numeracy, this has doubled.
The Xeon system has multiple cores, so you can open more stack overflow Windows at once to learn without slowing down your ALT-TAB.

Well, these are all jokes. As others have done well here, standard programming tasks do not need to be the grandest. But… If you are programming for a mobile device. I’m surprised no one mentioned this. I guess mobile programmers are too busy.

Intel Xeon CPU provides better virtual machine support. This is crucial for programming on mobile devices! Programming a mobile device requires the system to run an Android virtual machine. This is a burdensome process that will bend a 3.5GHz 4-core processor. So, in this case, the more cores the better. You want a high-core number. Especially if you are writing an application that communicates with each other, you will need to have multiple emulators open. Probably 2 and 4 emulators open is not unheard of. This is where the 16-core Xeon comes in handy, especially in a 2-slot configuration with 32 cores in total.
You may need more memory, at least 16 GB, and I recommend 32 GB or more. Xeon supports 768 GB of memory. There’s no problem here. The Android emulator requires the same amount of RAM as a real device. This means that if you are emulating Android with 4 GB of memory, you will have the VM allocated at least 4 GB. Not including OS, IDE, browser, which requires about 6 GB. Not to mention writing an application that requires two or more devices to communicate with the CEAH Other. To simulate four devices, each of which requires 4 GB of communication with each other, you will need 16 GB of memory for the VM only. Your operating system, IDE, and browser are not included. Now that the Android emulator is coming with 6 GB of memory, you’ll soon run out of the i7’s 32 GB limit. With a memory limit of 768 GB, Xeon seems to be the better choice.
You need more storage devices, such as 2 x 512 GB PCI-e SSDs in RAID 0 for super-fast storage, and 1 x 1 TB standard hard disk drives for backup. The Xeon has more PIC-E channels than the I7S, which means more PCI-E can be used. Sometimes a stupid error requires a reboot of the Android VM. If you write a game that requires four devices to communicate, you will need to restart four VMs, which will take a lot of time. Having more PCI-E channels is convenient because you can provide PCI-E SSD storage for each VM. Trust me, waiting for an emulated Android to load from the standard single SATA SSD that is shared with operating system drives is counterproductive.

This is my mobile programming experience. My VM was slow to load due to SSD, and I was running out of 16 GB of RAM and processor cores. It can be really annoying when you find out that you just mistyped < sign to > and the application just crashed. Take time to debug, recompile, and reload, but the problem is still there.

But… If you’re just learning to program, making simple applications, doing competitive programming, Web programming, and running PHP MySQL locally, then an Intel i3 or AMD A8 system with 8 GB of memory will suffice.

You can upgrade to Xeon while doing mobile programming.

However, if you are getting serious (and crazy), such as using the VMing LAMP stack on your own PC, Xeon is your best bet. I’d rather build a cheap, small LAMP server.



Leave a message