3 Replies Latest reply: Nov 20, 2010 8:52 AM by MarioGrgic
airflyer172 Level 1 Level 1 (0 points)
Unboxed my new 2.53 i5 4GB ram 7200 rpm Hatachi 500GB as replacement for my 09' 2.53 core 2 duo which I will be giving to my son. Core 2 is running new Seagate Momentous 500 7200 RPM drive (I kept the 250 as it had lots of data, point is replaced and reformatted the new drive).

Out of box new i5 seemed slow so I immediately reinstalled OS and WOW new i5 averaged 45.2 seconds + or - about .8 sec on successive reboots. Core 2 averages 31.6 +- .4 seconds! That is 14 seconds SLOWER for the i5.

So I think hard drive. Pop it out and get a new Segate Momentous same drive and model number as I put in the core 2. Now boot time is 43.4 seconds +- .3 on successive reboots. Core 2 still right there with 31.6. DISAPPOINTING!

Please not there is nothing goofy with the software each is running 10.6.5 and both are configured EXACTLY the same with the EXACT same harddrive. Seems that the i5 is substantially slower in boot up. Also noted it in application opening. i5 slightly slower. WHAT IS UP!

Any one with ideas? Could it have to do with buffering onboard graphics to RAM Core 2 is running nvidia only and is running nvidia memory hub and northbridge I think. Is this new unit on an Intel? and is it integrated?

MacBook Pro, Mac OS X (10.6.5), MacBook i5
  • 1. Re: New i5 Macbook slower than core 2
    eww Level 9 Level 9 (52,975 points)
    Given that there's hardly ever any reason to shut either machine down, I wouldn't worry about boot times at all.

    Do the two machines both have the same amount of RAM installed?

    Message was edited by: eww
  • 2. Re: New i5 Macbook slower than core 2
    yutokey Level 1 Level 1 (0 points)
    i have a i5 2.4 and the Momentus XT. It takes it 24 seconds to boot up..
  • 3. Re: New i5 Macbook slower than core 2
    MarioGrgic Level 1 Level 1 (40 points)
    I'd be really surprised if boot time was CPU bound. It's most definitely an I/O issue and it may not be as simple as HD speed either.

    It can have a lot to do with boot cache and fragmentation. iDefrag does a good job of de-fragmenting, but boot cache is system managed and it should be automatically re-created. You can see boot cache statistics and other things by running:

    $ sudo BootCacheControl -f /var/db/BootCache.playlist statistics
    initiated reads 4023
    blocks read 598016
    read errors 0
    blocks discarded by error 0
    batch 0 time 2.346s
    batch 1 time 14.520s
    blocks read in batch 0: 115316
    blocks read in batch 1: 482700
    blocks read in batch 2: 0
    reader thread rate 17728kB/s, 238tps
    total strategy calls 14374
    non-read strategy calls 2197
    throttled strategy calls 3154
    bypassed strategy calls 6371
    bypasses while active 755
    filled strategy calls 8003
    filled during active I/O 2792
    preload time 1.943s
    active time 59.421s
    read/write strategy rate 204/36tps
    callers blocked 23
    extents in cache 4020
    extent lookups 9027
    extent hits 7987
    extent hit ratio 88.48%
    hits not fulfilled 0
    blocks discarded by write 400
    blocks requested 420390
    blocks hit 353821
    blocks lost from cache 80
    block hit ratio 84.16%
    leftover blocks 243715
    block wastage 40.75%
    history clusters 17
    $