First *real-world* benches of Barcelona?

Page 4 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Gary Key

Senior member
Sep 23, 2005
866
0
0
Originally posted by: dmens
Originally posted by: Gary Key
Gary are you saying that the part scales better than linear? Interesting...

Not exactly, I cannot go into the details yet, just imagine the cache/memory pipeline as being a supercharger on a car, you have an engine (same compression ratio/cubic inches for NA versus SC) that performs the same until you hit a certain RPM/air-fuel mixture where the SC comes online and the power curve changes dramatically compared to the NA engine. The same basis is occurring here, all of the changes/enhancements made to the core / HT/ cache / memory controller are basically "idle" in some cases (SC is flowing more air than than the engine can take advantage of at low RPM plus you have parasitic drag from powering the SC), if not a hindrance (low compression and mismatched gearing). An engine (CPU) is most efficient at its torque peak (wherever that happens to be based on gearing, displacement, compression, efficiency, etc) and in this case, it starts nearing it (torque peak) around 2.4GHz from all indications.

Except a CPU has static resources, whereas a car engine can burn more fuel because a supercharger fed it compressed air. CPU core frequency increases cannot never yield greater than a linear performance gain.

I am not saying that increases in the CPU core frequency yield a linear performance gain greater than 1:1. My example as stated was crude and too simple, in this case the cubic inches, compression ratio, and gearing are static, the supercharger simply lets the engine perform more efficiently (from a power output perspective) by taking greater advantage of the fuel/air intake mixture (plus aggressive timings) it has available as RPMs rise.

Probably a very bad example, but I was trying to make the point that the changes in the architecture of this processor and the new chipsets (HT 3.0, etc) do not provide any advantages (in most cases) over the current platforms in performance until the core clock speed increases and we start to notice that around 2.4GHz (see below for other reasons at this time). I think I have said this several times since Computex, AMD desperately needs to get the core speeds on this processor architecture improved (above 2.4GHz or so, privately a few people at AMD agree) for it to be really competitive and to take full advantage of their processor/platform improvements.

I do not think AMD ever intended or even believed this CPU would launch at the speeds it will (1.8~2.0, possibly 2.2 in Q4) as the processor simply does not perform as efficiently as it should (appears capable of) based upon the architecture changes. A lot of the early information we had was that Barcelona would launch in the 2.2~2.4 range and then scale quickly, with a potential to 4GHz in the end. The early performance expectations and claims of performance improvements over current platforms were based on simulations at 2.4~2.6GHz and then scaling upwards. The CPU was designed with these speeds and above in mind, it simply is too slow right now not to mention several core improvements have been flipped on/off or just are not as efficient as they should be in early testing.

At least with the early samples we have seen, there are improvements against current processors on a clock for clock basis as the core speed improves, this does not mean a linear performance gain that is greater than 1:1, it simply means the chip is operating more efficiently as the core speed improves. There could be a wide variety of reasons for this as we have seen dramatic changes in the platform performance almost week to week as new steppings, chipet revisions, and BIOS code were changed. We have seen HT not working or set at 1.0, 2.0, 3.0 specifications depending upon core speed and chipset, secondary caches turned off or even gated based upon core speed (L3 cache and L2 prefetchers as late as July), floating-point instructions flipped on or off, out of order execution of load algorithms flipping from conservative to aggressive and back depending upon core speed, and even translation lookaside buffers being tinkered with during this time not too mention a dozen other changes.

Also remember that the DRAM controller is now split into two separate 64-bit controllers. Each controller can be operated independently by the chipset and there can be some significant improvements in efficiency, especially where the individual cores are working on independent threads and each have their own memory access patterns, yet another area where core speeds could create variable results. Added to this is the fact that the data prefetcher now brings data directly into the low latency L1 data cache, as opposed to the L2 cache in the K8. K10 also increased the ability of its L1 instruction cache prefetcher to handle two outstanding requests to any address. These two areas plus the new DRAM prefetcher on the revised memory controller are the control mechanisms that we have noticed having the greatest impact on performance, especially with the increase in core speed. It is also the area that believe has been most "tinkered" with during the prototype and pre-production phases. We have noticed the processors only needing DDR2-667 in June to really being responsive with DDR2-1066 as the core speeds have increased along with the other improvement/additions to the processor, BIOS, and chipsets.

When I said that certain features were "idle" in some cases, this is what I was talking about. Until we see production level silicon and final BIOS code, it is extremely difficult to determine what is occurring inside Barcelona/Phenom and what is not on a clock for clock basis. Throw into that mix, a whole new generation of chipsets (ie...RD790) that take further advantage of these changes and you have a situation that is very fluid as the initial performance results will be on older HT 2.0 chipsets that are designed for the enterprise environment. There is not a consumer level board available that is tuned for this processor series yet, trying to use it on one is like using a QX6850 on a VIA PT880, yeah it works, but look at the results.

That is why we do not want to guesstimate the performance or even provide tangible numbers until we have had a chance to test released product. For whatever reason, in the early tests, the processor operated more efficiently as the core speed increased, we will find out shortly why it did. I hope this helps and if I could speak in greater detail, I would, but September 10th is getting close. Like I said in my previous message, some people will be happy, some will not, and most will realize that certain hype does not directly translate into expected performance improvements, not until we see some speed (counting on this). ;) In the end, this processor lays the groundwork for what comes next, sort of like how the Core Series did for the Core 2 (imho).
 

SerpentRoyal

Banned
May 20, 2007
3,517
0
0
Ahhh...more scoops. Releasing an un-refined product will only alienate loyal AMD customers. They should delay the release of Barcelona until the product can be competitive with the higher-end Intel CPUs. Sometimes, you have to walk away from a bad design and focus your resources on other endeavours. If it takes another year to release a competitive non-Barcelona CPU, so be it. Never pour good $ into a black hole. AMD doesn't have the luxury of time/$ to work out all the bugs in Barcelona.
 

BitByBit

Senior member
Jan 2, 2005
474
2
81
Originally posted by: Gary Key

Not exactly, I cannot go into the details yet, just imagine the cache/memory pipeline as being a supercharger on a car, you have an engine (same compression ratio/cubic inches for NA versus SC) that performs the same until you hit a certain RPM/air-fuel mixture where the SC comes online and the power curve changes dramatically compared to the NA engine. The same basis is occurring here, all of the changes/enhancements made to the core / HT/ cache / memory controller are basically "idle" in some cases (SC is flowing more air than than the engine can take advantage of at low RPM plus you have parasitic drag from powering the SC), if not a hindrance (low compression and mismatched gearing).

This is not only a poor choice of analogy, but bears no resemblance to CPU scaling. An internal combustion engine does not produce a linear power/RPM graph, even in highly tuned engines, due to the difficulties in feeding the engine, plus energy loss due to friction and heat. Superchargers are driven by the engine, and as such provide optimum compression at higher RPM. This is a compound effect, since higher compression leads to higher RPM, and higher RPM leads to higher compression. This compound effect is entirely absent in CPUs, since processors do not need to 'force' data into the core. The Athlon 64's Integrated Memory Controller runs at the same speed as the core, meaning that memory latency is reduced with clock speed. This does not mean that IPC increases with clock speed, but rather, memory access latency in cycles remains more constant, allowing IPC to scale more linearly.

An engine (CPU) is most efficient at its torque peak (wherever that happens to be based on gearing, displacement, compression, efficiency, etc) and in this case, it starts nearing it (torque peak) around 2.4GHz from all indications.

The IPC a processor can sustain at any frequency is dependent upon access latency and to a lesser extent bandwidth. Internal latencies will always be the same, since cache runs at the same speed as the core, but external latencies (in CPU cycles) will degrade along with clock speed. Large caches and intelligent prefetching ensure that the impact of this is minimal through fewer external accesses, but their efficiency remains the same at any clock speed. As a result, processors do not have a 'peak torque', but rather an IPC that degrades slightly as clock speed increases.


I do not think AMD ever intended or even believed this CPU would launch at the speeds it will (1.8~2.0, possibly 2.2 in Q4) as the processor simply does not perform as efficiently as it should (appears capable of) based upon the architecture changes. A lot of the early information we had was that Barcelona would launch in the 2.2~2.4 range and then scale quickly, with a potential to 4GHz in the end. The early performance expectations and claims of performance improvements over current platforms were based on simulations at 2.4~2.6GHz and then scaling upwards. The CPU was designed with these speeds and above in mind, it simply is too slow right now not to mention several core improvements have been flipped on/off or just are not as efficient as they should be in early testing.

Efficiency will not increase with clock speed. The improvements made to K10 may well ensure its IPC/Frequency relationship remains more linear, but K10 will be no more efficient in terms of IPC at 2.4GHz than at 1.8GHz.

Also remember that the DRAM controller is now split into two separate 64-bit controllers. Each controller can be operated independently by the chipset and there can be some significant improvements in efficiency, especially where the individual cores are working on independent threads and each have their own memory access patterns, yet another area where core speeds could create variable results. Added to this is the fact that the data prefetcher now brings data directly into the low latency L1 data cache, as opposed to the L2 cache in the K8. K10 also increased the ability of its L1 instruction cache prefetcher to handle two outstanding requests to any address. These two areas plus the new DRAM prefetcher on the revised memory controller are the control mechanisms that we have noticed having the greatest impact on performance, especially with the increase in core speed. It is also the area that believe has been most "tinkered" with during the prototype and pre-production phases. We have noticed the processors only needing DDR2-667 in June to really being responsive with DDR2-1066 as the core speeds have increased along with the other improvement/additions to the processor, BIOS, and chipsets.

These improvements all increase IPC, but do not function more efficiently at higher clock speeds. IPC will still degrade along with clock speed, but perhaps to a lesser extent.

When I said that certain features were "idle" in some cases, this is what I was talking about. Until we see production level silicon and final BIOS code, it is extremely difficult to determine what is occurring inside Barcelona/Phenom and what is not on a clock for clock basis. Throw into that mix, a whole new generation of chipsets (ie...RD790) that take further advantage of these changes and you have a situation that is very fluid as the initial performance results will be on older HT 2.0 chipsets that are designed for the enterprise environment. There is not a consumer level board available that is tuned for this processor series yet, trying to use it on one is like using a QX6850 on a VIA PT880, yeah it works, but look at the results.

I've never heard of any case whereby features become active at certain clock speeds. If this is indeed the case, then my apologies, but it doesn't make sense. Why would AMD deactivate features at lower clock speeds?

 

Arkaign

Lifer
Oct 27, 2006
20,736
1,379
126
Thanks Gary Key for your kind and forthcoming communique re: K10.

I think by features not being active, he may be running K10s with and without certain features enabled. This may be an issue of the chipset revision, and drivers.

In short : K10 is ready. Platform is not. They may be testing K10 at lower HT/Bus speeds, with processor features disabled, etc, just to make it work for the moment. This would account for more than a 1:1 improvement from where it stands at the juncture we see it at, but due to enabling features, increasing HT/bus speeds, reducing latencies, etc, than on the actual clock speed increase itself.

I still think it's somewhat misleading to have given the impression that more than a 1:1 ratio performance/frequency could be met on equal conditions (increasing clock speed only, no other improvements/tuning/revision). But thanks for clarifying Gary, you've made a lot more sense in this last post.
 

Stoneburner

Diamond Member
May 29, 2003
3,491
0
76
So, we still have no idea how barcelona is going to perform. To hell with it, i'm going back to my 686 cyrix
 

Amaroque

Platinum Member
Jan 2, 2005
2,178
0
0
686 Cyrix? No way! I'm going back to my 386 SX 16 MHz... ;)

If I may interpret (don't shoot me). With pre-production silicon, some functions are on, and some are off, at a given point in time (random).
 

VirtualLarry

No Lifer
Aug 25, 2001
56,587
10,227
126
Originally posted by: Accord99
Because you are comparing two different families of CPU. But for one CPU, a 33% increase in clockspeed at best will only result in a 33% increase in performance. And since most applications require memory access, HD access or video card, then that 33% increase in clockspeed starts to diminish in importance since the application is not spending all of its time in the CPU.
That's the biggest problem with all of these new CPUs. With the rest of the system performance (HD, memory) remaining essentially the same - some applications perform no better on a faster system than on a slower one. My Athlon XP 2000+ (1.6Ghz), runs things like QuickPAR just as fast as my new C2D E4400 (2.8Ghz) system does. However, the C2D runs DVDShrink much, much faster than the Athlon. So the upgrade was worth it, but it doesn't speed up everything, some tasks are still HD-bound.

The performance gap is only going to be worse with desktop quad-core systems, especially if you attempt to multi-task apps that all require disk access. In that case, the HD will thrash, and overall performance will drop BELOW what you could achive with a single-core CPU.


 

DesertCat

Junior Member
Jun 5, 2006
7
0
0
I really appreciate the information in this thread as it gives insight into the whole development process. The thing that makes me nervous is all of the talk about needing the newest chipsets. This all focuses on upgradability of current systems and whether the new processors will perform acceptably on them.

Of course we are talking about Barcelona and not Phenom at this point, but the huge question in my mind is whether dropping a Phenom into my current Nvidia 570 motherboard will make any sense at all? Last year all of the talk was about how these AM2+ processors would be backwards compatible with AM2 motherboards, just without HT3 and some power management features. It still leaves me wondering if this will be an OK thing to do with these processors or if they will be hobbled too much. When Phenom comes out I hope Anandtech does an article comparing a fullblown AM2+ system and a Phenom in an AM2 system. I would be very interested.
 

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
Originally posted by: VirtualLarry
That's the biggest problem with all of these new CPUs. With the rest of the system performance (HD, memory) remaining essentially the same - some applications perform no better on a faster system than on a slower one. My Athlon XP 2000+ (1.6Ghz), runs things like QuickPAR just as fast as my new C2D E4400 (2.8Ghz) system does. However, the C2D runs DVDShrink much, much faster than the Athlon. So the upgrade was worth it, but it doesn't speed up everything, some tasks are still HD-bound.

The performance gap is only going to be worse with desktop quad-core systems, especially if you attempt to multi-task apps that all require disk access. In that case, the HD will thrash, and overall performance will drop BELOW what you could achive with a single-core CPU.

VirtualLarry you have no idea how absolutely spot-on you are in this assessment.

The type of tasks I throw at the computer involve random access of 576 files. To keep my computer from choking on random access time I set it up with raid-0 Ramdisk from gigabyte and house the critical files in a ramdisk.

My simulations complete much much faster because of this arrangment.

For anything which is not I/O bound, i.e. truly CPU limited, ratcheting up processor speed at Moore's law pace is super. But for those applications which truly grind on the I/O you really need to invest your time and effort (as a systems integrator) in making sure the weakest link (hard-disk I/O) is improved whenever and wherever possible.
 

bryanW1995

Lifer
May 22, 2007
11,144
32
91
Originally posted by: Arkaign
Originally posted by: bryanW1995
Originally posted by: Arkaign
Originally posted by: classy
Originally posted by: Arkaign
This alone will have the potential value to increase AMD's ASP so that they stop hemmoraghing cash, which if they do not staunch, will destroy AMD before Q3 '08, perhaps sooner.


Hey look I am not a fanboy so I could care less who gets destroyed ok, so calm down. sheesh...... I am just simply stating the statement dmens made about clock speed is not entirely true. Simply put, the platform alone can do more with the same cpu cycles. So in the case of AMD with barcy, it is quite possible that the platform can bring about better performance percentage wise in comparison to clock speed increase, Thats all I am saying.

I don't need to calm down, I wasn't shouting at anyone. I want AMD to survive, and they need to take drastic action soon to make that happen. They've lost nearly 2 BILLION dollars in 3 quarters. This is unsustainable, and to recover they need to increase their ASP. If their product remains inferior to the competition, it is impossible to raise the ASP, as next to noone will pay a premium for a weaker product, without brand/market control.

One more time : all other factors remaining the same, cpu performance cannot exceed a 1:1 ratio. It's never been done, and doesn't make any kind of logical sense whatsoever. This truth is impossible to refute with any credibility. A variance of less than 1% on one benchmark when all others show less than a 1:1 increase is proof of only the variance that you inevitably see in benchmark results. It's why averaging many benchmark runs is so important.
2 things:
1. See GM or Ford info if you think that losing 2billion in 3 quarters is unsustainable.
2. observer-created reality makes a lot less sense than a 1:1 or greater scaling ratio of cpus.

GM and Ford are many many many many times larger than AMD, and the auto market is far more stable than electronics.
I'm in the auto industry, I know a lot about GM and Ford both. Comment was tongue in cheek.

 

bryanW1995

Lifer
May 22, 2007
11,144
32
91
Originally posted by: SerpentRoyal
Ahhh...more scoops. Releasing an un-refined product will only alienate loyal AMD customers. They should delay the release of Barcelona until the product can be competitive with the higher-end Intel CPUs. Sometimes, you have to walk away from a bad design and focus your resources on other endeavours. If it takes another year to release a competitive non-Barcelona CPU, so be it. Never pour good $ into a black hole. AMD doesn't have the luxury of time/$ to work out all the bugs in Barcelona.
they already walked away from k9, they would get bitten (sorry, couldn't resist) if they left k10 behind, too. Seriously, how could you recommend that they completely walk away from it??? They have to make it work, and, according to what gary said, it appears that they can still have a successful product once the clock speeds ramp up.
 

Markfw

Moderator Emeritus, Elite Member
May 16, 2002
27,394
16,236
136
Originally posted by: VirtualLarry
Originally posted by: Accord99
Because you are comparing two different families of CPU. But for one CPU, a 33% increase in clockspeed at best will only result in a 33% increase in performance. And since most applications require memory access, HD access or video card, then that 33% increase in clockspeed starts to diminish in importance since the application is not spending all of its time in the CPU.
That's the biggest problem with all of these new CPUs. With the rest of the system performance (HD, memory) remaining essentially the same - some applications perform no better on a faster system than on a slower one. My Athlon XP 2000+ (1.6Ghz), runs things like QuickPAR just as fast as my new C2D E4400 (2.8Ghz) system does. However, the C2D runs DVDShrink much, much faster than the Athlon. So the upgrade was worth it, but it doesn't speed up everything, some tasks are still HD-bound.

The performance gap is only going to be worse with desktop quad-core systems, especially if you attempt to multi-task apps that all require disk access. In that case, the HD will thrash, and overall performance will drop BELOW what you could achive with a single-core CPU.

SCSI raid-0, 5 disks, can you say fast ?? The problem is money.
 

bryanW1995

Lifer
May 22, 2007
11,144
32
91
150 gb raptors in raid 0 are only about $320 AR and will keep you rollin' for quite a while.
 

SerpentRoyal

Banned
May 20, 2007
3,517
0
0
Originally posted by: bryanW1995
Originally posted by: SerpentRoyal
Ahhh...more scoops. Releasing an un-refined product will only alienate loyal AMD customers. They should delay the release of Barcelona until the product can be competitive with the higher-end Intel CPUs. Sometimes, you have to walk away from a bad design and focus your resources on other endeavours. If it takes another year to release a competitive non-Barcelona CPU, so be it. Never pour good $ into a black hole. AMD doesn't have the luxury of time/$ to work out all the bugs in Barcelona.
they already walked away from k9, they would get bitten (sorry, couldn't resist) if they left k10 behind, too. Seriously, how could you recommend that they completely walk away from it??? They have to make it work, and, according to what gary said, it appears that they can still have a successful product once the clock speeds ramp up.

If K10 isn't competitive now, then it's not going to be competitive six months from now. This is especially true if one must settle on high-speed/low latency DDR2 RAMs that may not reach the market in sufficient number promote lower prices. Intel will continue to push for DDR3. Intel is still moving forward with better CPUs with higher core speed.

Windows ME anyone?

 

BitByBit

Senior member
Jan 2, 2005
474
2
81
Originally posted by: PlasmaBomb
Higher RPM doesn't lead to higher compression.

No, I just made it up.

"...This makes the maintenance of smoothly increasing RPM far harder with turbochargers than with belt-driven superchargers which apply boost in direct proportion to the engine RPM."
Source

Clearly.


 

BitByBit

Senior member
Jan 2, 2005
474
2
81
Originally posted by: SerpentRoyal
If K10 isn't competitive now, then it's not going to be competitive six months from now.

How do you know? K10 won't be competitive on release, but 6 months from now we will surely see much higher clocked versions that can compete.

This is especially true if one must settle on high-speed/low latency DDR2 RAMs that may not reach the market in sufficient number promote lower prices. Intel will continue to push for DDR3. Intel is still moving forward with better CPUs with higher core speed.

Given there are still no credible benchmarks out, how can you imply its performance is going to depend on fast RAM? Does K8? The improvements made to K10's memory controller, the addition of L3 cache and improved prefetching will actually reduce the impact of memory latency and therefore reduce the need for faster RAM.
 

Nemesis 1

Lifer
Dec 30, 2006
11,366
2
0
Originally posted by: BitByBit
Originally posted by: PlasmaBomb
Higher RPM doesn't lead to higher compression.

No, I just made it up.

"...This makes the maintenance of smoothly increasing RPM far harder with turbochargers than with belt-driven superchargers which apply boost in direct proportion to the engine RPM."
Source

Clearly.

You and PlasmaBomb are not talking apple to apples here .Your both right and wrong. I have noticed BitByBit has tendency to take things out of context.

On a naturually asperated engine airflow will not increase compression at higher rpms. If you stuff the cyclinders with force feed air . Yes compression will in fact rise depending on how the waste gates are set up.

Back on topic and to the point. In the beginning AMD created the K10 and after it went to the fabs . AMD was able to test results and it was not good. But Amd kept putting out info that sugjested it would be so much more than C2D. Now that AMD has been able to test these mircle native chips . They have changed how they talk about K10. They went from 40% more performance than K10 talk . To we are about as fast as C2D but have better price performance than C2D. Problem is If AMD sells K10 for $266 . They won't make any $$. As we already know from recent Qt. reports. The other problem is this Penryn will be Better Cost performance than AMD.

As for Intels cost it will be much lower than K10 65nm. As penryn will be 45nm.

I here many people saying wait till AMD gets new steppings. I am waiting for new steppings but not AMD. Intels penryns the ones most people have seen are A0 steppings and they are great. Intel for doing a die shrink with C2D to penryn is said not to be a big deal
Again I say hold back the BS please . Intel penryn is on a totally new process period High K and metal gates. A0 steppings doing what they are doing is nothing short of a mircle. Wait until you see what the B0 steppings can do. Than their will be B1 steppings.
This race for performance per watt is over Intel penryn isn't released nor is K10 but this thing is over befor it even starts. This is infact taking all the BS rumors of the past year and keeping them in context . Penryn >K10 or K10< Penryn .
Thats it . We have 9 days left and this will all be laid to rest. Thank god.

I would like to see K10 win . But at the same time I don't . WHY? Because if K10 wins. It will be 9 months of Nehalem speculation . 3 months isn't bad but 1 year of K10 bs. has turned me off to this part of speculation . That and the fact that if Intel leads in performance the rules change on posting. 20% improvement in performance goes from great to its not that much faster . and you really can't see the differance in real world terms. I can prove this simply by going back and reading post when AMD lead in performance by 10% in some apps not all. Than it was great 10% made all the differance in the world.

I laugh at YOU!

 

BitByBit

Senior member
Jan 2, 2005
474
2
81
Originally posted by: Nemesis 1
You and PlasmaBomb are not talking apple to apples here .Your both right and wrong. I have noticed BitByBit has tendency to take things out of context.

My post was in response to the implication of similarities between CPUs and engines, where none really exist. You've 'noticed' I take things out of context? Are you sure that isn't your own false interpretation from poor understanding? Stop talking BS.

On a naturually asperated engine airflow will not increase compression at higher rpms. If you stuff the cyclinders with force feed air . Yes compression will in fact rise depending on how the waste gates are set up.

A naturally aspirated engine is not what we were talking about. The subject was superchargers, which provide greater compression at higher RPM.

I suggest you properly read the posts you attempt to refute.

 

Nemesis 1

Lifer
Dec 30, 2006
11,366
2
0
Originally posted by: BitByBit
Originally posted by: Nemesis 1
You and PlasmaBomb are not talking apple to apples here .Your both right and wrong. I have noticed BitByBit has tendency to take things out of context.

My post was in response to the implication of similarities between CPUs and engines, where none really exist. You've 'noticed' I take things out of context? Are you sure that isn't your own false interpretation from poor understanding? Stop talking BS.

On a naturually asperated engine airflow will not increase compression at higher rpms. If you stuff the cyclinders with force feed air . Yes compression will in fact rise depending on how the waste gates are set up.

A naturally aspirated engine is not what we were talking about. The subject was superchargers, which provide greater compression at higher RPM.

I suggest you properly read the posts you attempt to refute.

It wasn't I who was confused Plasma bomb was. He was also correct.
As for taking things out of contect . Tell me smarty pants what would happen to a blower engine if the waste gates weren't set. At a perdetremined setpoint. I know but do you. Your right a blower will increase compression as rpm rises. But waste gates are required to make sure the cylinders are not over stuffed or engine will detonate. So blower will increase compression only up to a certain setpoint otherwise BOOM! It is a good anology to k10 tho as you can draw the conclusion that the waste gates = Core issue . K10 is 3 issue. So less compression at higher RPM. C2D is 4-5 issue so waste gate pressure is much higher . More compression = more work = higher performance.

 

Pabster

Lifer
Apr 15, 2001
16,986
1
0
Originally posted by: bryanW1995
I'm in the auto industry, I know a lot about GM and Ford both. Comment was tongue in cheek.

Hmm, GM, Ford, and AMD ... all sinking ships. Coincidence? :laugh:

Now seriously, I expect Barcelona to be pretty competitive. But I don't think it will be enough. Too little, too late. And that's a damn shame, because we're going to see chip prices increase.
 

Nemesis 1

Lifer
Dec 30, 2006
11,366
2
0
Originally posted by: Pabster
Originally posted by: bryanW1995
I'm in the auto industry, I know a lot about GM and Ford both. Comment was tongue in cheek.

Hmm, GM, Ford, and AMD ... all sinking ships. Coincidence? :laugh:

Now seriously, I expect Barcelona to be pretty competitive. But I don't think it will be enough. Too little, too late. And that's a damn shame, because we're going to see chip prices increase.

Were is this proof of chip pricing going higher if K10 loses. The proof is just the opposit of what your saying. C2D brought prices down because it was easier for Intel to produce than P4 and the smaller process.

If K10 wins only than will we see prices go higher. Either way the price war is almost over so prices will stablize or go higher. AMD can't make $$ at this level and we have proof of that. Were as Intel is making 46% margins right now with 65nm . When they go to 45nm margins for intel will rise. AT the present price points. I would really like to see K10 win this one by at least 30% than we shall see who raises prices.

 

BitByBit

Senior member
Jan 2, 2005
474
2
81
Originally posted by: Nemesis 1
It wasn't I who was confused Plasma bomb was. He was also correct.
As for taking things out of contect . Tell me smartly pants what would happen to a blower engine if the waste gates weren't set. At a perdetremined setpoint. I know but do you. Your right a blower will increase compression as rpm rises. But waste gates are required to make sure the cylinders are not over stuffed or engine will detonate. So blower will increase compression only up to a certain setpoint otherwise BOOM! It is a good anology to k10 tho as you can draw the conclusion that the waste gates = Core issue . K10 is 3 issue. So less compression at higher RPM. C2D is 4-5 issue so waste gate pressure is much higher . More compression = more work = higher performance.

Are you sure you're not confused?
 

Greenman

Lifer
Oct 15, 1999
22,462
6,552
136
I had assumed that since AMD hasn't leaked any benchmarks, K10 was a loser. It just seems obvious to me that if you have a killer part you leak information to build a little excitement. My guess is that K10 will be a hum-drum cpu.

 

SerpentRoyal

Banned
May 20, 2007
3,517
0
0
Originally posted by: BitByBit
Originally posted by: SerpentRoyal
If K10 isn't competitive now, then it's not going to be competitive six months from now.

How do you know? K10 won't be competitive on release, but 6 months from now we will surely see much higher clocked versions that can compete.

This is especially true if one must settle on high-speed/low latency DDR2 RAMs that may not reach the market in sufficient number promote lower prices. Intel will continue to push for DDR3. Intel is still moving forward with better CPUs with higher core speed.

Given there are still no credible benchmarks out, how can you imply its performance is going to depend on fast RAM? Does K8? The improvements made to K10's memory controller, the addition of L3 cache and improved prefetching will actually reduce the impact of memory latency and therefore reduce the need for faster RAM.


Then you should wait another six months for Barcelona to mature.