Which processor will need a case re-design? That's what I'm interested in.
Everybody is harping on about 64bit this and 64bit that. Unless you are using software that has been specifically architected to use 64bit then you're not going to get any improvement because you're still bound by the 32 bit laws of memory = 4Gb max !!! 64bit gives you massive speed improvements when dealing with +4gb data - especially when multi threading it.
Also, note that even using the same software architected in 64bit mode compared to 32bit mode has a memory footprint increase... even using the same database and/or file...
Montevina could speed up that wait
I doubt so, I used to be a PC user and remember having to shell out top dollar for the "latest DDR2" memory as well as paying premiums for that "revolutionarily new Intel chipset with a faster Front Side Bus". In retrospect it is all nonsense.
If I can afford to wait, sure, why not.
But to be honest, I would wait just so I can buy the last generation of processors and memory at cheaper price. Paying twice as much for the "latest XXX Mhz" of memory has never paid of during my gaming days, that is for sure.
It is all hype.
well that must have been a while back but technology is a bit different these days and certainly frontside bus of difference of 1066mhz as to 800mhz is a HUGE difference. Sure ddr2 compared to ddr3 you wont notice much on the gpu/ram side on games. And your mainly comparing a gpu/ram specs as a gamer and not the overal usage of the whole osx. And dont forget windows cant even address more than 3.5 gb of ram and does a poor job doing so.
Just try encoding videos and render effects on a imac as to a mac pro with the same amount of ram and tell me you dont see a difference. Honestly gaming and real computing usage is two totally different things.
P
The fact is, for most users, Montevina won't mean too much. Nehalem, the next CPU, will be the big upgrade. Frankly, I wouldn't be surprised if Apple waits for Nehalem to do a redesign too. I just don't think performance wise the June update (if there is one) will be all that great for the vast majority of users.
People involved in professional video and such are some of the few who may really realize a performance gain. The fact is, for what MOST average computer users do (internet stuff, iPhoto, music/iTunes, YouTube, the occasional family video, maybe PowerPoint and lots of word processing for work) computers of 3 years ago are more than sufficient. For the average user, games are the ONLY thing that will come close to taxing modern computer equipment. The fact you need a better "rig" for the hottest games than you do for high-powered scientific applications is, to me, ludicrous, and one reason I have moved largely to consoles, but that's for another post.
The fact is, for most users, Montevina won't mean too much. Nehalem, the next CPU, will be the big upgrade. Frankly, I wouldn't be surprised if Apple waits for Nehalem to do a redesign too. I just don't think performance wise the June update (if there is one) will be all that great for the vast majority of users.
As an aside, thank you to the OP for this post. I get SO tired of all the Macolytes saying "I upgraded from my SR MBP to Penryn." No, you didn't. You still have Santa Rosa. You upgraded from MEROM to Penryn.
Montevina also has X4500 intel GMA
X3100*3 = X4500
As an aside, thank you to the OP for this post. I get SO tired of all the Macolytes saying "I upgraded from my SR MBP to Penryn." No, you didn't. You still have Santa Rosa. You upgraded from MEROM to PENRYN
From a technical standpoint, Montevina is going 'open' the communication lines in laptops. Right now things are still slow, (just what I feel) and things need to be opened up more, QuickPath Interconnects are going to help big time with internal I/O latencies, and hopefully open up bandwith to graphics etc...
In all honesty, all these questions of when the next MBP is coming is tiring. The best bet is to look at other manufacturers and see when they are planning and when their product refresh cycles are about to happen. Everyone just moved to Penryn, and will be the chip to get us threw the summer months, now come fall/holiday time the question will be...will Intel push everyone to move Montevina or wait until Jnauary/Feb 09 after the holidays and drop the penryns chips price down for the holiday buying market.
In my opinion its all up to Intel and what kind of pressure they put on the manufacturers and what plans they have to when to release a new processor (and I dont mean paper launch i mean acutally available in 'x' amount of quatities).
We shall see..ya never know what these guys are going to do next.
I know this has actually been said before but Montevina and Santa Rosa are actually platforms. The Santa Rosa platform uses an Intel Mobile GM965 chipset code named Crestline.Okay, I make it easy for you to understand:
Chipset : Montevina, SantaRosa
Processor : Penryn, Merom
Understand? Its really simple, like I said, Intel would be changing either chipset or processor in average of 6 months, so expect Apple to have minor changes around 6 months and maybe a big one after a year.
Chipset : a group of integrated circuits designed to work together (this is where you are going to see new integrated GPU and etc)
Processor : like its name, it processes your commands. Or in another word
you can call it laborer .
Perhaps it would be easier to refer to these components using the model numbers/names rather than code names to avoid confusion.
I do see your point in a way but the proliferation of code names appears to cause confusion. Montevina will be the first platform in the Centrino 2 lineup - this has been confirmed by Intel.From my opinion, codename make it much easier to remember just you must get used with the names,
I find it harder to communicate if we use code cause its pretty hard to remember, GM45? Whats that? Cantiga? Why the weird name?
You get what I mean right?
Its odd that Intel platform names is much easier and sounds better then their chipset or processor real name.
Oh yeah Montevina is rumoured to be Centrino 2.