<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Nachricht</TITLE>
<META content="MSHTML 6.00.2800.1126" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=322552908-01082003><FONT face=Arial color=#0000ff size=2>Sure -
from <A
href="http://minnow.cc.gatech.edu/squeak/3272">http://minnow.cc.gatech.edu/squeak/3272</A></FONT></SPAN></DIV>
<DIV><SPAN class=322552908-01082003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=322552908-01082003>
<H3>Starting Squeak on Windows</H3>
<UL>
<LI><B>The naive way</B><BR>Double click on the Squeak VM (Squeak.exe). Note
that this method has some disadvantages. Since the VM does not know what image
file to use it must search the disk. I have seen this method to take various
seconds to complete. In addition, if there is none or more than one image file
you will be prompted with a file dialog to select the one you want to use.
</LI></UL></SPAN></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=de dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
squeak-dev-bounces@lists.squeakfoundation.org
[mailto:squeak-dev-bounces@lists.squeakfoundation.org] <B>On Behalf Of
</B>Dean_Swan@Mitel.COM<BR><B>Sent:</B> Friday, August 01, 2003 4:51
AM<BR><B>To:</B> The general-purpose Squeak developers list<BR><B>Subject:</B>
RE: Startup time, a short review &
discussion<BR><BR></FONT></DIV><BR><FONT face=Courier size=2>Hi Andreas &
John,</FONT> <BR><BR><FONT face=Courier size=2>For what it's worth, I have two
Windows NT 4 machines and a Windows ME machine, and here are some very
approximate (i.e. measure with a clock on the wall) startup times for
Squeak3.2-4956 using Squeak 3.2.3/Tea 1.8 VM (release from Sep 5 2002,
compiler gcc 2.95.2 19991024 (release).</FONT> <BR><FONT face=Courier
size=2>My idea of startup time is time from double-click on Squeak.exe until
the Squeak window appears.</FONT> <BR><BR><FONT face=Courier size=2>CPU
OS
Physical Startup
Time Bytecodes
Sends</FONT> <BR><FONT face=Courier size=2>
RAM</FONT> <BR><FONT face=Courier size=2>1.4 GHz Pentium 4
WinNT4SP5
512M
~16 seconds
~119M/Sec ~2.90M/Sec</FONT>
<BR><FONT face=Courier size=2>450 MHz Pentium II
WinNT4SP6 256M
~18 seconds
~ 44M/Sec
~1.26M/Sec</FONT> <BR><FONT face=Courier size=2>700 MHz Pentium III
WinMe
128M
~ 2 seconds
~ 67M/Sec ~1.94M/Sec</FONT>
<BR><BR><FONT face=Courier size=2>These are very coarse measurements, but the
two NT machines take about the same time to start up and the ME machine is
much, much faster, while tinyBenchmarks more closely reflects the clock speeds
of the CPU.</FONT> <BR><BR><FONT face=Courier size=2>Any ideas to explain
this?</FONT> <BR><BR><BR><FONT face=Courier size=2>
-Dean</FONT> <BR><BR><FONT
face=Courier size=2> </FONT><BR><FONT face=Courier
size=2> </FONT><BR><BR><BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<TD><FONT face=sans-serif size=1><B>"Andreas Raab"
<andreas.raab@gmx.de></B></FONT> <BR><FONT face=sans-serif
size=1>Sent by: squeak-dev-bounces@lists.squeakfoundation.org</FONT>
<P><FONT face=sans-serif size=1>07/31/03 08:00 PM</FONT> <BR><FONT
face=sans-serif size=1>Please respond to The general-purpose Squeak
developers list </FONT> <BR></P>
<TD><FONT face=Arial size=1> </FONT><BR><FONT
face=sans-serif size=1> To:
"'The general-purpose Squeak developers list'"
<squeak-dev@lists.squeakfoundation.org></FONT> <BR><FONT
face=sans-serif size=1> cc:
</FONT> <BR><FONT face=sans-serif size=1>
Subject: RE: Startup time, a
short review & discussion</FONT></TR></TBODY></TABLE><BR><BR><BR><FONT
face="Courier New" size=2>> I've been glancing at squeak startup time on
the mac this <BR>> morning and have a few observations. Actually I have
noticed on<BR>> windows the images "SNAP' open, but take seconds on the mac
and I'd <BR>> like to fix that...<BR><BR>Another thought: Is it
possible that you're allocating the memory lazily and<BR>the image loading
process hits the exception handler upon first access to<BR>each memory page?
This might slow down things quite a bit. In the Windows VM<BR>I am actually
pre-allocating the memory needed for the image data (plus some<BR>extra)
before the read comes along to avoid this.<BR><BR>Cheers,<BR> -
Andreas<BR><BR><BR></FONT><BR><BR></BLOCKQUOTE></BODY></HTML>