<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
@font-face
{font-family:"Myriad Web Pro";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.eda6f675-3506-4dff-925f-94dfe434e74e, li.eda6f675-3506-4dff-925f-94dfe434e74e, div.eda6f675-3506-4dff-925f-94dfe434e74e
{mso-style-name:eda6f675-3506-4dff-925f-94dfe434e74e;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>I’m no software engineer but I thought that’s how processors were supposed to work (one application per thread). I’ve ran into the same problem on larger complex projects. If that’s true, a higher clock speed may be the only solution.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><b><span style='color:#0F243E'>Anthony Hardman, PE<o:p></o:p></span></b></p><p class=MsoNormal><b><span style='font-size:9.0pt;color:#0F243E'>LEED AP BD&C</span></b><b><span style='color:#0F243E'><o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:10.0pt;color:#0F243E'>Building Performance Analyst<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#0F243E'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='color:#00B050'>THE GREEN ENGINEER, LLP</span></b><b><span style='color:#00B050'><o:p></o:p></span></b></p><p class=MsoNormal><b><span style='color:#00B050'>Sustainable Design Consulting – Energy Modeling – LEED Project Management </span></b><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#0F243E'>50 Beharrell St<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#0F243E'>Concord, MA 01742<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#0F243E'>O: 978/610-2801<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#0F243E'>C: 720/840-7862<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#0F243E'><o:p> </o:p></span></p><p class=MsoNormal><a href="http://www.greenengineer.com/"><span style='font-size:10.0pt;text-decoration:none'><img border=0 width=49 height=47 id="Picture_x0020_1" src="cid:image001.jpg@01CC1623.ED30B340" alt="Description: TGE Logo"></span></a><a href="http://www.linkedin.com/in/ahardman81"><span style='color:#1F497D;text-decoration:none'><img border=0 width=52 height=47 id="Picture_x0020_2" src="cid:image002.jpg@01CC1623.ED30B340" alt="Description: images5"></span></a><a href="http://twitter.com/#!/a_Hardman"><span style='text-decoration:none'><img border=0 width=49 height=47 id="_x0000_i1028" src="cid:image006.jpg@01CC1623.ED30B340" alt="Description: t4"></span></a><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#0F243E'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Jeremy McClanathan<br><b>Sent:</b> Thursday, May 19, 2011 12:45 PM<br><b>To:</b> 'Brian Tysoe'; equest-users@lists.onebuilding.org<br><b>Subject:</b> Re: [Equest-users] Multithreading<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>I had the same problem and our IT guy did a similar analysis and came to the same conclusion. The CPU was the bottleneck. I upgraded to a Dell Precision T3500 and it reduced my open time on a large hospital project from 10 minutes to 1.5 minutes.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Myriad Web Pro";color:gray'>___________________________________________</span></b><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#5F5F5F'>Jeremy McClanathan</span></b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:gray'>, </span><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray'>LEED<sup>®</sup> AP BD+C</span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='line-height:9.0pt'><b><span style='font-size:8.0pt;font-family:"Verdana","sans-serif";color:#5F5F5F'><img border=0 width=98 height=15 id="Picture_x0020_8" src="cid:image007.jpg@01CC1623.ED30B340" alt="CDi_Engineers_logo_color.jpg"></span></b><b><span style='font-size:8.0pt;font-family:"Verdana","sans-serif";color:olive'><o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray'>4200 194th St SW, Ste 200, Lynnwood, WA 98036</span><b><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:olive'><o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray'>P 425-672-1071 | F 425-778-8769 </span><span style='font-family:"Verdana","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:13.5pt;font-family:Webdings;color:#99CC00'>P</span><span lang=EN-GB style='font-family:Webdings;color:#99CC00'> </span><i><span lang=EN-GB style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#99CC00'>Please consider the environment before printing this email.</span></i><span style='color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Brian Tysoe [mailto:BTysoe@mcw.com] <br><b>Sent:</b> Thursday, May 19, 2011 11:06 AM<br><b>To:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> [Equest-users] Multithreading<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-CA>Hello equest-users,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Does anyone out there know if the next release of eQuest (based on a new version of DOE 2 I believe) will be able to make use of processor multithreading?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>We are running into problems modelling large buildings with eQuest 3.64. Files are taking upwards of 5 minutes to open and once they are open it takes about 8 seconds to modify any single field. If you want to change the flow rate of an AHU you enter your number and then wait for 8 seconds while the software thinks about it.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>We have done some monitoring and found that the software is running on one processor core at 100% and that is the bottleneck.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Exhibit A: Loading the model<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA><img border=0 width=565 height=489 id="Picture_x0020_4" src="cid:image008.png@01CC1623.ED30B340" alt="Description: cid:image001.png@01CC1628.DD97AE70"><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>In this graph (taken while loading the model) you can see that eQUEST’s CPU usage is constant. It is only using one of the available CPU cores and it is using that core to the max. Compare this to the Disk usage and you can see that the Disk usage spikes up several times but those spikes are relatively low.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Exhibit B: Changing values<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA><img border=0 width=861 height=544 id="Picture_x0020_3" src="cid:image009.png@01CC1623.ED30B340" alt="Description: cid:image002.png@01CC1628.DD97AE70"><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>In this graph you can see the CPU usage spike up when I made a change in eQUEST and then dip down several seconds after. The Disk usage is still sporadic and low.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>We have concluded that adding RAM will not speed things up. The best solution is a faster processor.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Has anyone else done any similar benchmarking and want to share their findings?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-CA>Brian Tysoe </span></b><span lang=EN-CA>M.A.Sc., P.Eng., LEED AP <o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-CA>Mechanical Engineer </span></i><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA><a href="http://www.mcw.com" title="Click here to visit www.mcw.com"><b><i><span style='color:green;text-decoration:none'>MCW Consultants Ltd. </span></i></b></a><o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-CA>600-156 Front Street West <br>Toronto, ON M5J 2L6 <br>Phone 416-598-2920 <br>Fax 416-598-5394 </span></i><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA> <o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-CA>This e-mail may be privileged and confidential. Any unauthorized use is strictly prohibited. If you received this e-mail in error, please contact the sender directly. </span></i><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=eda6f675-3506-4dff-925f-94dfe434e74e><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray'>This email message, including any attachments, is for the sole use of the intended recipient and may contain confidential, proprietary, and/or privileged information, as well as content subject to copyright and other intellectual laws. If you are not the intended recipient, you may not disclose, use, copy, or distribute the email message or its attachments. If you believe you have received this email message in error, please contact the sender by reply email, immediately delete this email and destroy copies.</span><o:p></o:p></p></div></body></html>