C＃项目在更快的新工作站上在Visual Studio中构建SLOWER [英] C# project builds SLOWER in Visual Studio on faster, new workstations
问题描述
我们订购了具有快速硬件和出色规格的新系统，但Visual Studio
构建项目所需的时间比旧工作站要长。 Msbuild比b $ b更快，csc.exe更快，文件复制更快。但是打开将
项目文件从一个工作站直接复制到新工作站，
在新工作站上本地打开项目，然后运行Build from
$ IDE中的b $ b，它更慢 - 更慢，比如30秒而不是10
秒。 输出窗口不指示差异。我们从两个工作站区分了
输出日志，只看到新工作站上的更短的msbuild时间。
当在新工作站上构建时，Visual Studio暂时冻结，在此过程中大约三到四次（-ish）
（我没算过）。 Visual Studio冻结的时间总和大约相当于完成所有内容所花费的额外时间。
输出
窗口确实* NOT *显示它开始冻结时的工作原因因为
每次都在一个完全不同的位置。但是基于输出日志中非常小的
差异，它*似乎*在某个地方略有不同
围绕它计算要导入或解析的依赖项的位置br />
路径。但是我还没准备好认为这可能是相关的。
新旧工作站都有WD Raptor驱动器，2GB RAM（新的
工作站@800MHz），两者都在AMD上运行（旧工作站运行
单核Athlon，新工作站运行双核Athlon 6000+），
Windows Server 2003（带有SP2的新工作站，既没有工作站运行
R2，程序[vs后台服务]配置为优先级），
和带有Service Pack 1的Visual Studio 2005。 br />
有什么想法吗？
- Jon
We ordered new systems with fast hardware and great specs, but Visual Studio
takes longer to build a project than on the old workstation. Msbuild is
faster, csc.exe is faster, file copy is faster. But opening copying the
project files straight over from one workstation to the new workstation,
opening the projects locally on the new workstation, and running Build from
within the IDE, it''s slower--much slower, like 30 seconds rather than 10
seconds. The Output window does not indicate differences. We diff''d the
Output log from the two workstations and only see shorter msbuild times on
the new workstation.
When building on the new workstation, Visual Studio temporarily freezes up,
about three or four times (-ish) during the process (I haven''t counted). The
sum amount of time that Visual Studio freezes is roughly equivalent to the
extraneous amount of time it takes for everything to complete. The Output
window does *NOT* show what it''s working on when it starts freezing because
it''s in a completely different spot each time. But based on very minor
differences in the Output log it *seems* to be slightly different somewhere
around where it''s calculating which dependencies to import, or resolving
paths. But I''m not ready to think that''s probably related.
Both the old and new workstations have WD Raptor drives, 2GB RAM (new
workstation @800MHz), both running on AMD (old workstations running
single-core Athlons, new workstation running dual-core Athlon 6000+),
Windows Server 2003 (new workstation with SP2, neither workstations running
R2, and Programs [vs Background Services] are configured to have priority),
and Visual Studio 2005 with Service Pack 1.
Any ideas?
- Jon
推荐答案
Jon Davis< jo*@REMOVE.ME.PLEASE.jondavis.netwrote：
< snip>
Jon Davis <jo*@REMOVE.ME.PLEASE.jondavis.netwrote:
<snip>
旧的和新的工作站都有WD Raptor驱动器，2GB RAM（新的
工作站@ 800MHz），两者都在AMD上运行（旧工作站运行
单核Athlon ，新工作站运行双核心Athlon 6000+），
Windows Server 2003（带有SP2的新工作站，既没有工作站运行
R2，程序[vs后台服务]也配置为优先级），
和带有Service Pack 1的Visual Studio 2005.
有什么想法吗？
Both the old and new workstations have WD Raptor drives, 2GB RAM (new
workstation @800MHz), both running on AMD (old workstations running
single-core Athlons, new workstation running dual-core Athlon 6000+),
Windows Server 2003 (new workstation with SP2, neither workstations running
R2, and Programs [vs Background Services] are configured to have priority),
and Visual Studio 2005 with Service Pack 1.
Any ideas?
他们是否运行相同的病毒扫描软件？
-
Jon Skeet - < sk *** @ pobox.com>
http：// www。 pobox.com/~skeet 博客： http：//www.msmvps。 com / jon.skeet
如果回复小组，请不要给我发邮件
Are they running the same virus scanning software?
--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
我应该补充一下，我们有有几次重新启动，我们已经尝试更换内存，而实际上我们在其他基于英特尔的新工作站上遇到了同样的问题
（所有多核）。
我不能不认为它与Windows中的默认配置相关
a）某些东西不同在我们旧的工作站环境中，尽管在新的
工作站上安装了SP2，为Visual Studio安装了SP1，甚至导入了Vi sual Studio
设置从旧工作站到新工作站使用
工具 - >选项团队设置文件导入工具，
或b）多个核心。但是我没有听说过有人遇到这个问题吗？
多核心？
我希望别人看到这个。
Jon
I should add, we have had several reboots, we''ve tried swapping out RAM, and
in fact we had the same problem on other new workstations based on Intel
(all multiple core).
I can''t help but think that it''s related to either
a) default configuration in Windows that something somehow is different in
our old workstation environments, despite having installed SP2 on the new
workstation and SP1 for Visual Studio and even importing the Visual Studio
settings from the old workstation onto the new workstation using the
Tools->Options team settings file import tool,
or b) multiple cores. But I haven''t heard of anyone having this problem with
multiple cores??
I''m hoping someone else has seen this.
Jon
4月17日下午4:18，Jon Davis < j ... @ REMOVE.ME.PLEASE.jondavis.net>
写道：
On Apr 17, 4:18 pm, "Jon Davis" <j...@REMOVE.ME.PLEASE.jondavis.net>
wrote:
我应该添加，我们有过几次重新启动，我们已经尝试更换内存，而实际上我们在其他基于英特尔的新工作站上遇到了同样的问题
（所有多核）。 br />
我不能不认为它与Windows中的默认配置相关
a）某些东西在某种程度上是不同的
我们旧的工作站环境，尽管在新的
工作站和Visual Studio的SP1上安装了SP2，甚至从Visual Studio导入了Visual Studio
设置旧工作站使用
工具 - >选项团队设置文件导入工具进入新工作站，
或b）多个核心。但是我没有听说过有人遇到这个问题吗？
多核心？
我希望别人看到这个。
Jon
I should add, we have had several reboots, we''ve tried swapping out RAM, and
in fact we had the same problem on other new workstations based on Intel
(all multiple core).
I can''t help but think that it''s related to either
a) default configuration in Windows that something somehow is different in
our old workstation environments, despite having installed SP2 on the new
workstation and SP1 for Visual Studio and even importing the Visual Studio
settings from the old workstation onto the new workstation using the
Tools->Options team settings file import tool,
or b) multiple cores. But I haven''t heard of anyone having this problem with
multiple cores??
I''m hoping someone else has seen this.
Jon
好吧，如果你有双核并且处理器速度低于on
您的旧机器会发现速度变慢。由于编译只能在一个核心上发生，因此它会变慢。否则我不是真的好b $ b看看为什么会慢一些。
Well if you have a dual core and the processor speed is lower than on
your older machines you will notice a slow down. Since compiling can
only happen on one core it will be slower. Otherwise I don''t really
see why it would be slower.
这篇关于C＃项目在更快的新工作站上在Visual Studio中构建SLOWER的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
