Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, May 25, 2017 10:08 AM
Hi.
I am preparing my next PC build and need help choosing between AMD (Ryzen) and Intel 7th gen based platforms for working with VS 2017.
I am looking for a platform that is fully supported and fully utilized by Visual Studio, Blend and Resharper, especially when working with complex projects in XAML.
What system wold be the choice for best performance without being an overkill?
Thanks!
<strike>Lets say i want to build a new PC this August (2017) year and need help choosing between AMD (Ryzen) and Intel 7th gen based platforms for working with VS 2017. I have spotted a post with people having problems with Android emulator and I was wondered if there is anything else that I should take into consideration before making a choice.</strike>
- <strike>are there any features of Visual Studio 2017 that will not be supported on AMD?</strike>
- <strike>can anyone tell if VS benefits from having more (8) cores with lower frequencies or fewer (4) cores with higher frequencies? For example, I will be using XAML (UWP, WPF) and Blend quite heavily.</strike>
- <strike>what to expect from the compilation times on two systems?</strike>
- <strike>any general rules when making such decisions?</strike>
<strike>I am also using R# in VS, and it looks like it tries to do in parallel as much is possible, and probably is a ryzen/reason for more cores.</strike>
All replies (15)
Friday, May 26, 2017 3:16 AM
Hi Tridy,
Welcome to the MSDN forum.
Usually, we discuss one issue in one thread, it will help us to research and trace your issues, thank you for your understanding.
Please have a look at Visual Studio 2017 Product Family System Requirements and check the Hardware requirements as below:
- 1.8 GHz or faster processor. Dual-core or better recommended
- 2 GB of RAM; 4 GB of RAM recommended (2.5 GB minimum if running on a virtual machine)
- Hard disk space: 1GB to 40GB, depending on features installed
- Video card that supports a minimum display resolution of 720p (1280 by 720); Visual Studio will work best at a resolution of WXGA (1366 by 768) or higher
And the additional requirements like the following, which may be relates to your issues:
- For emulator support, Windows 8.1 Pro or Enterprise (x64) editions are required. A processor that supports Client Hyper-V and Second Level Address Translation (SLAT) is also required.
- Universal Windows app development, including designing, editing, and debugging, requires Windows 10. Windows Server 2016 and Windows Server 2012 R2 may be used to build Universal Windows apps from the command line.
If the AMD or Inter meet the above requirements, you can choose the suitable one per your condition.
Since our forum is to discuss the VS IDE, to be honest I am not very familiar with the hardware, on my side, I used Processer: Inter(R) Core(TM) i7-4790 CPU @ 3.6GHz and my OS is Windows 10 which good compatibility with VS 2017 versions.
Maybe you can consult with the hardware suppliers to give some suggestions to configure your computer from some other aspect, since they are the experts in terms of hardware. Sorry for this inconvenience and thank you for your understanding.
Best regards,Sara
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].
Saturday, May 27, 2017 9:22 AM
Thanks for the answer, Sara.
Let me paraphrase my question to be more IDE specific:
"Windows 10 running Visual Studio 2017. Will VS2017 IDE work 100% on Amd Ryzen platform?"
As far as I can see, any Intel i3, i5, i7 processors will have no problems with Hyper-V and SLAT. It looks like AMD will do Hyper-V and SLAT as well. However all this is in theory. I would not be able to return back a motherboard or a processor based on the missing feature in motherboard BIOS even though the processor supports it and things like that.
To prove the theory, I would like to hear from people who have done work on Ryzen platform with VS 2017 and can confirm that it works in the mentioned scenarios.
thanks
Saturday, May 27, 2017 9:43 AM
Be aware getting an answer in this forum means nothing. Nobody is responsible here for what they writes as it is they think it is, at the moment they write it. If they have other insight a second after that. Yea what then.
If you really want an answer then contact Microsoft in your country.
https://www.microsoft.com/en-us/worldwide.aspx
Success
Cor
Tuesday, August 29, 2017 11:40 AM
Hi Tridy,
I am about to make the same decision as you: Intel or AMD for my next development rig?
As it is now August I am hoping you have come to a conclusion and made your decision.
Hence I am curious: Which giant did you choose for, why and if you choose for AMD - What is your experience?
Thanks in advance for sharing and greetings from Germany,
Peter Vrenken
Tuesday, August 29, 2017 12:01 PM | 1 vote
Hi.
Lets say i want to build a new PC this August (2017) year and need help choosing between AMD (Ryzen) and Intel 7th gen based platforms for working with VS 2017. I have spotted a post with people having problems with Android emulator and I was wondered if there is anything else that I should take into consideration before making a choice.
- are there any features of Visual Studio 2017 that will not be supported on AMD?
- can anyone tell if VS benefits from having more (8) cores with lower frequencies or fewer (4) cores with higher frequencies? For example, I will be using XAML (UWP, WPF) and Blend quite heavily.
- what to expect from the compilation times on two systems?
- any general rules when making such decisions?
I am also using R# in VS, and it looks like it tries to do in parallel as much is possible, and probably is a ryzen/reason for more cores.
Thanks.
One word answer for your many questions: INTEL!
If you like this or another reply, vote it up!
If you think this or another reply answers the original question, mark it or propose it as an answer.
Mauricio Feijo
www.mauriciofeijo.com
Tuesday, August 29, 2017 12:12 PM | 2 votes
...
One word answer for your many questions: INTEL!
Do you think I would bother posting the questions if I wanted a fanboy-type answer?
Tuesday, August 29, 2017 12:38 PM
Hi Tridy,
I am about to make the same decision as you: Intel or AMD for my next development rig?
As it is now August I am hoping you have come to a conclusion and made your decision.
Hence I am curious: Which giant did you choose for, why and if you choose for AMD - What is your experience?
Thanks in advance for sharing and greetings from Germany,
Peter Vrenken
Hi.
I am still planning my build with Calyos fanless case and they have delayed it until December. So, I still have quite some time before that.
My decisions so far:
I have not found anything that would stop me from going AMD for Visual Studio development. I will go for Ryzen 1800x, not Threadripper which would be an overkill.
At this point, comparing 1800x to Intel's option of 7700K, I am going towards more cores, where 1800x wins. Maybe Intel will release something similar before December, then I will consider that as well.
I think that going 16 cores and paying much more for both the processor and motherboard will not give benefits when working in Visual Studio. Well, maybe if you are opening 8 instances of Visual Studio then it could be the case. The power consumption and how much heat is being produced is also something to consider even if you have money to get the top price rig (Threadripper and Intel's X-Series based). To me, it looks like Ryzen platform is getting mature enough and I am starting to feel comfortable about it.
The rest of the parts (power supply, memory, drives. graphics) is a different story and are the same for both blue and red based systems, so that was not the point of the discussion.
Tuesday, August 29, 2017 1:01 PM
...
One word answer for your many questions: INTEL!
Do you think I would bother posting the questions if I wanted a fanboy-type answer?
Tridy,
You are right, and I apologize. My joke was unwarranted.
To meet the Forum's guidelines I suggest you follow our limits of one question per post, as Sara Liu mentions above.
If you like this or another reply, vote it up!
If you think this or another reply answers the original question, mark it or propose it as an answer.
Mauricio Feijo
www.mauriciofeijo.com
Tuesday, August 29, 2017 1:32 PM
...
To meet the Forum's guidelines I suggest you follow our limits of one question per post, as Sara Liu mentions above.
Is that why I did not really get any answers? :)
I will re-write the posting to be more argument-like rather than questions-like.
Tuesday, August 29, 2017 1:48 PM
...
To meet the Forum's guidelines I suggest you follow our limits of one question per post, as Sara Liu mentions above.
Is that why I did not really get any answers? :)
I will re-write the posting to be more argument-like rather than questions-like.
Yes, that will probably help. You can also post as a Discussion rather than a Question.
If you like this or another reply, vote it up!
If you think this or another reply answers the original question, mark it or propose it as an answer.
Mauricio Feijo
www.mauriciofeijo.com
Friday, November 17, 2017 9:15 AM
Hi Tridy,
This is my experience so far:
I needed to replace my word PC and decided to take the Ryzen plunge on the 1700x on X370 Asus Motherboard. For everything else besides Visual Studio the system is running great. I changed too many variables (moved from win 7 to win 10, changed disk, changed VS versions) so read the following with that in mind.
For Visual Studio, I used 2013 mainly on my old rig and decided to move to 2015. Most of my work is in COM - 2015 is down right unusable in debugging. It takes 5 seconds to step over a simple System.Diagnostics.Trace.WriteLine("") and the longer VS is open the worse it gets. I have tried the suggestions for optimising 2015 by turning off some of the features, but the problem still persists.
2013 is better and faster, but it still feels much much slower than my old PC. I am searching for solutions (which is how I encountered your post). At the same time my colleague did a re-install as well. Software wise very similar. Hardware is Intel platform and he doesn't have any issues.
I am still in the process of investigating why this is happening. I will post if I manage to solve it. As reference here is my PC spec:
Asus Prime X370-A
AMD Ryzen7 1700x
16GB (2x8GB) Corsair vengence LPX DDR4-3000
Samsung 250GB 960 EVO NGFF(M.2)
Coolermaster Hyper 212 Turbo Cooler
Corsair CX550M Power Supply
Palit GTX 1060 3GB
I've installed the latest BIOS updates and drivers. I've tried the various Ryzen performance tweaks as recommended on the various posts. Visual Studio 2015 and 2013 just do not run well at all.
So in response to the pertinent question -
Does Visual Studio run well on Ryzen? :- On my setup at this point in time. Not at all.
Friday, November 17, 2017 2:32 PM
Just some feedback.
Been messing around with settings on the motherboard and I have done the following:
- Turned off turbo clock
- Set memory to Channelled
- Set VDDCR settings in AI Suite all to extreme (performance)
I have also adjusted the fan curves to be a bit more aggressive, but that shouldn't be an issue the CPU was hovering around 45c and now is down to 40c.
After the tweaks and a reboot it looks to be much faster. I will have to sit with it a while to see if it is indeed fixed. So to revise, perhaps VS will run fine, but it will probably mean that you will have to tinker to get it to run stable.
Others have had issues with other IDEs:
https://www.reddit.com/r/Amd/comments/632ozc/developers_ryzen_feel_slow_on_win_10_turn_on/
Here are some of the performance tweaks
https://mspi.es/blog/5-Performance-Tweaks-for-Visual-Studio-2015-and-large-solutions
I also disabled the optimised debugger
Friday, March 9, 2018 9:27 PM
Thanks for the feedback and tips, Sanctuary.
It is interesting that Visual Studio does not demand much CPU which stays cool. So, your observations prove one more time that fast RAM and especially SSD is more important. It also sounds strange that modern processors would not be able to handle full solution analysis and should be disabled for the optimization purposes. I wonder what will happen if you add Resharper on top of that.
As about my story, I haven't purchased the parts for the new build yet, because Calyos NSG-S0 has been delayed for several times now, and I really wanted to build a fanless system for home. Plus, the pricing for the graphics cards and RAM has been really high last months. I will wait a little bit more to see where it will bring me by the end of the summer or so. I still have an idea of getting more cores for Visual Studio and I will see what kind of options there will be after the summer.
We will be getting new machines at work within a couple of months or so, and I am thinking about staying on the "safe side" there with Intel, giving Hades Canyon NUC a try at this point. I think it has a good balance of everyhing to be a great dev office machine. It is like a very good notebook but inside a relatively small case.
I will get back when I have something to share.
Once again, thanks for sharing the Ryzen experience and tips.
Saturday, March 10, 2018 9:04 AM
This is interesting because I have had the exact opposite experience. I haven't touched any of the settings beyond enabling the XMP profile in the BIOS and the Ryzen processor that I have has been working just as well compared to the previous Intel processor that I used.
However, I am a C++ developer so my experience is with the C++ project engine.
This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because the major point of my posts is to aid in the learning process.
Saturday, March 10, 2018 2:01 PM
You cant have too much power for Visual Studio.
VS soaks up a lot of CPU power for some functions.
Time is money so the faster the better.
n.Wright