I thought I would pitch in my build times:
On i7 MBP with SSD, when booted natively into Windows 7 64bits - 9 min
32 sec
Same but virtualized with 4 cores and 4 Gb ram: 15 min 10 sec
Ivan
On 8/29/13 9:36 AM, Weijun Wang wrote:
I have watched this thread for some time. Yes, SSD should be faste
Hi, After trying the following with no significant improvement
- remove Norton 360 anti-virus
- defrag hard file
- upgrade cygwin and java boot jre
- remove the search index attribute from all files on the entire hard file
- turned off some processes that seemed to be using disk cycles: Acronis
Tru
Hi Ioi, Now that the HOTSPOTMKSHOME env var is pointing at my cygwin
directory...
On 8/28/13 9:32 PM, Ioi Lam wrote:
> Pete,
>
> By the way, for the purposes of testing your build speed, instead of
> spending a long time building JDK8, maybe you can just build hotspot.
> It's not completely propor
Hi Ioi, Here's what I got this time, pointing at jdk8 b73 which was
downloaded from the EA site -Pete
c:\Users\Pete\JDK8\jdk8\hotspot\make\windows>create c:\Users\Pete\jdk1.8.0
cygwin warning:
MS-DOS style path detected:
c:\Users\Pete\JDK8\jdk8\hotspot\/make/windows/get_msc_ver.sh
Preferred PO
Hi Pete,
create.bat is a script in thehotspot\make\windowsdirectory.
It needs a parameter that points to a valid JDK 8 build. I have
d:\re\jdk8-b102\windows-i586on my PC, but need to change that to point
to where you put the JDK.
- Ioi
On 09/04/2013 08:14 AM, Pete Brunet wrote:
create d:\r
Hi Erik, Getting caught up on email...
On 8/30/13 2:08 AM, Erik Joelsson wrote:
> Two more questions:
>
> Are you building 32 or 64bit and how many jvm variants? I built 64bit
> so only server.
I am only building 32 bit. My config/make invocations are:
bash ./configure --with-freetype=/cygdrive/
Hi loi, I tried what you suggested and got the following. What other
steps do I need to take? -Pete
Setting environment for using Microsoft Visual Studio 2010 x86 tools.
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC>cd
c:\Users\Pete\JDK8\jdk8\hotspot\make\windows
c:\Users\Pete\JDK8\jd
Hi Dimitri,
On 8/13/13 9:19 AM, Dmitry Samersoff wrote:
> Peter,
>
> 1. When you "turn norton off" it's actually still hook all opens, so
>significantly slow down things.
>
>Try to create exclusion rule to exclude your build directory from
>protection.
At least for now I uninstalled it.
Hi Pete,
a very silly question but are you sure you are using the new build?
Maybe you can post your complete configure and make commands and your
environemnt?
Your build times really look like the ones from the old build. What
build times did you had for building jdk7 for example?
Regards,
Volke
Two more questions:
Are you building 32 or 64bit and how many jvm variants? I built 64bit so
only server.
What boot jdk are you using? 32 or 64bit? You haven't accidentally put a
debug build there or something? I'm using a 64bit jdk7u something,
probably 4 or 7, can't access the machine to c
Besides removing Norton 360 I defragged my disk with Auslogics Disk
Defrag. The disk was quite fragmented prior to running the defragger
but neither of those helped much. Current situation:
WinSat disk:
Average Read Time with Sequential Writes 23.026 ms
Latency: 95th Percentile
--with-java-devtools and J: or /java is a network mounted share?
-DrD-
> I have watched this thread for some time. Yes, SSD should be faster but
> Pete's build times are just incredibly slow and there must be some other
> reason.
>
> I just open my Lenovo t410 (i5 2.6GHz, 8GB RAM, HDD) that h
On 2013-08-28 23:30, Pete Brunet wrote:
On 8/28/13 6:21 AM, Erik Joelsson wrote:
Nice to see improvement, but it's still far from where it should be.
For comparison, here are my build times on a similar, but probably
slower, laptop. Lenovo T410, i5 M 520 2.40GHz and 4GB ram, no ssd.
This lapto
I have watched this thread for some time. Yes, SSD should be faster but
Pete's build times are just incredibly slow and there must be some other
reason.
I just open my Lenovo t410 (i5 2.6GHz, 8GB RAM, HDD) that has been
asleep for the last two days, mkdir a new directory, run configure and
"m
Dell laptop (Win7, i5-2520M 2.5Ghz, 8GB RAM) + Samsung 840 PRO SSD 256GB.
The JDK source tree is excluded from virus scan.
The source has all the open and closed parts. I ran configure and "make
all" with all default parameters.
- Build times ---
Start 2013-08-28 20:33:57
End 2013-
Pete,
By the way, for the purposes of testing your build speed, instead of
spending a long time building JDK8, maybe you can just build hotspot.
It's not completely proportional but would give you some ideas whether
you should consider getting another laptop :-)
Start Menu -> All Programs ->
On 08/28/2013 11:47 AM, Pete Brunet wrote:
Thanks Tim,
On 8/27/13 6:44 PM, Tim Bell wrote:
Good advice on the virus scanning front, and of course every bit helps.
Also keep in mind that laptop components often sacrifice performance
in favor of saving space, power, and battery life. A laptop i
On 29/08/2013 7:44 AM, Pete Brunet wrote:
On 8/28/13 2:11 PM, Tim Bell wrote:
On 08/28/13 11:47 AM, Pete Brunet wrote:
Since winset ran in a separate window and it closed before I could
use the info I needed this advice:
http://superuser.com/questions/93826/winsat-command-line-closes-too-fast
On 8/28/13 2:11 PM, Tim Bell wrote:
> On 08/28/13 11:47 AM, Pete Brunet wrote:
>
>> Since winset ran in a separate window and it closed before I could
>> use the info I needed this advice:
>> http://superuser.com/questions/93826/winsat-command-line-closes-too-fast
>> Running as admin solved it.
>
On 8/28/13 6:21 AM, Erik Joelsson wrote:
> Nice to see improvement, but it's still far from where it should be.
> For comparison, here are my build times on a similar, but probably
> slower, laptop. Lenovo T410, i5 M 520 2.40GHz and 4GB ram, no ssd.
> This laptop has no anti virus scanning install
On 08/28/13 11:47 AM, Pete Brunet wrote:
Since winset ran in a separate window and it closed before I could use
the info I needed this advice:
http://superuser.com/questions/93826/winsat-command-line-closes-too-fast
Running as admin solved it.
Or open a command window and type in the command
Thanks Tim,
On 8/27/13 6:44 PM, Tim Bell wrote:
> Good advice on the virus scanning front, and of course every bit helps.
>
> Also keep in mind that laptop components often sacrifice performance
> in favor of saving space, power, and battery life. A laptop is not a
> workstation.
>
> If your lapt
Pete,
One of ways to get rid of antivirus is to install VirtualBox, another
copy of windows into VirtualBox and do all unsafe internet access from
within this box.
-Dmitry
On 2013-08-09 18:44, Pete Brunet wrote:
> My product is Norton 360. To turn it off I right click on the Norton
> 360 icon
Nice to see improvement, but it's still far from where it should be. For
comparison, here are my build times on a similar, but probably slower,
laptop. Lenovo T410, i5 M 520 2.40GHz and 4GB ram, no ssd. This laptop
has no anti virus scanning installed.
- Build times ---
Start 2013-08-2
Good advice on the virus scanning front, and of course every bit helps.
Also keep in mind that laptop components often sacrifice performance in
favor of saving space, power, and battery life. A laptop is not a
workstation.
If your laptop drive is a sad little unit like mine, you pay and pay.
Peter,
It might be important for you to make sure the boot jdk image, and all tools
used to build (like VS2010) also in the ignore list. Maybe CYGWIN too.
The boot jdk rt.jar file in particular can be slow to virus scan.
It kind of depends on how smart (or not) the virus scanner is on re-scanning
Here are my release build times with my repo tree in the Norton 360 real
time virus checking ignore list:
00:03:34 corba
00:12:51 demos
00:15:10 docs
00:18:42 hotspot
00:15:55 images
00:01:42 jaxp
00:07:32 jaxws
00:43:04 jdk
00:04:17 langtools
00:02:31 nashorn
02:05:18 TOTAL
Here are the prior ti
Peter,
1. When you "turn norton off" it's actually still hook all opens, so
significantly slow down things.
Try to create exclusion rule to exclude your build directory from
protection.
2. Make sure you have SATA controller in AHCI but not legacy mode in a
BIOS, (make sure you have A
Sorry, Peter. Can't help you there... Any SSD is better than none as
long as it works in your T500 ;-)
On 09.08.13 18:25, Pete Brunet wrote:
Any suggestions for SSDs? My T500 takes 2.5" SATA II.
On 8/9/13 10:44 AM, Andreas Rieber wrote:
Hi Peter,
try perfmon.exe to see where the bottleneck
Any suggestions for SSDs? My T500 takes 2.5" SATA II.
On 8/9/13 10:44 AM, Andreas Rieber wrote:
> Hi Peter,
>
> try perfmon.exe to see where the bottleneck is. Most likely it is
> memory or io. If you have the option, go for a SSD drive (you will get
> build times ~10 minutes).
>
> Andreas
>
>
>
Hi Peter,
try perfmon.exe to see where the bottleneck is. Most likely it is memory
or io. If you have the option, go for a SSD drive (you will get build
times ~10 minutes).
Andreas
On 09.08.13 16:44, Pete Brunet wrote:
My product is Norton 360. To turn it off I right click on the Norton
3
My product is Norton 360. To turn it off I right click on the Norton
360 icon in the system tray and choose Disable Antivirus Auto-Protect.
If anyone knows if this is not sufficient and what else needs to be done
please let me know.
Pete
On 8/9/13 1:58 AM, Erik Joelsson wrote:
> I wonder if an
I wonder if anti virus is really turned off here. In my experience, it's
hard to make it stop completely. I have a slightly older laptop, same
brand, that builds this in around 40-45 minutes.
/Erik
On 2013-08-09 03:32, Pete Brunet wrote:
Haven't rebuilt a release version yet for a true compar
Haven't rebuilt a release version yet for a true comparison but here are
my fastdebug times with anti-virus turned off; about the same as release
with anti-virus on.
00:04:30 corba
00:07:25 demos
00:16:28 docs
00:16:15 hotspot
00:23:13 images
00:04:18 jaxp
00:07:29 jaxws
00:59:41 jdk
00:05:11 lang
4. Using a debug jdk as your boot jdk
:)
Langtools taking 6 minutes is crazy long. Since there is no native code there,
#1 would be my first guess.
-kto
On Aug 5, 2013, at 5:54 PM, Weijun Wang wrote:
> From my experiences there are 3 reasons a compile could be slow:
>
> 1. Anti-Virus program
#1 could be it in my case. I'll report back the next time I build
without that.
On 8/5/13 7:54 PM, Weijun Wang wrote:
> From my experiences there are 3 reasons a compile could be slow:
>
> 1. Anti-Virus programs
> 2. Virtual Machines
> 3. Network folders
>
> --Max
>
> On 8/6/13 12:48 AM, Pete Bru
From my experiences there are 3 reasons a compile could be slow:
1. Anti-Virus programs
2. Virtual Machines
3. Network folders
--Max
On 8/6/13 12:48 AM, Pete Brunet wrote:
Hi Erik,
00:05:55 corba
00:09:46 demos
00:15:00 docs
00:18:37 hotspot
00:17:13 images
00:03:32 jaxp
00:11:41 jaxws
01:05:
That's s feature, not a bug! :)
http://xkcd.com/303/
(Sorry, I couldn't resist)
Cheers,
Mario
Il giorno 02/ago/2013 22:26, "Pete Brunet" ha
scritto:
> FWIW I just built 32 bit jdk8 release on 64 bit win 7 with cygwin 1.7.21
> on a dual core 8 GB 2.53 GHz Lenovo T500 and the build time was 2:37
Hi Erik,
00:05:55 corba
00:09:46 demos
00:15:00 docs
00:18:37 hotspot
00:17:13 images
00:03:32 jaxp
00:11:41 jaxws
01:05:35 jdk
00:06:47 langtools
00:02:26 nashorn
02:37:45 TOTAL
Pete
On 8/5/13 6:55 AM, Erik Joelsson wrote:
> That was disappointingly slow for sure. Do you have the build time
> s
That was disappointingly slow for sure. Do you have the build time
summary listing?
/Erik
On 2013-08-02 22:26, Pete Brunet wrote:
FWIW I just built 32 bit jdk8 release on 64 bit win 7 with cygwin 1.7.21
on a dual core 8 GB 2.53 GHz Lenovo T500 and the build time was 2:37:45.
FWIW I just built 32 bit jdk8 release on 64 bit win 7 with cygwin 1.7.21
on a dual core 8 GB 2.53 GHz Lenovo T500 and the build time was 2:37:45.
41 matches
Mail list logo
