G70 has 32 pixel pipelines ?


Recommended Posts

With G70 now fully dissected we know have a little greater understanding of the part. Of course one element that characterises G70 is that of die size: its big.

Estimates of the die size put it in the order of around 330mm2, which on a 12" wafer would give in the order of around 150-170 full die to the wafer. Now, the issues here are one of yield - the fewer die there are on a wafer the more likely they are prone to defects. An analyst has suggested to us that there may be as many as 130-160 defects per wafer for earlier 110nm lines from TSMC (although the process is now more mature so that is likely to have decreased) which could give could potentially give very low yields for the chips should everyone need to work without any defects at all.

Now, one thing that we have been used to over the past few years releases is that of utilising defect cores in as lower performance products. The pixel pipelines, followed by the vertex pipelines, are taking the majority of the die space on products such as these and so a natural process defect is most likely to manifest itself in one of these areas; by disabling the pixel quad or vertex shader the defect has manifested itself in the IHV is then still able to recoup much of the cost of that particular piece of silicon, rather than wasting the entire die area.

The difference with G70 is that it is even larger than previous die sizes, which means that it is quite possible that full product yields may be quite small. Could it be that, in order to alleviate this, the defect rate is already built in to the current GeForce 7800 GTX and 24 fragment shaders is not the full number that G70 supports? Whilst many have speculated on an Ultra variant still to come and have been looking at the overclocks of the GTX’s to speculate where it may hit, perhaps it could be the case that there are 32 fragment pipelines in G70 and the fully working die are quietly being collected for use at a later date?

Source

This could mean Nvidia is selling the defective cores (those that dont have full 32 pixel pipelines) just like the 6800 vanilla but at a price point of $599. Anybody planning on buying the 7800GTX should hold off.

:whistle:

Link to comment
https://www.neowin.net/forum/topic/336336-g70-has-32-pixel-pipelines/
Share on other sites

Keep in mind that the terminology changes.  Pipelines aren't straight pipelines like they have been in the past.  The 7800 GTX has 24 fragment pipes with 16 ROPs, which means it can only output 16 pixels per clock.

586116616[/snapback]

Exactly, not a 'true' 24 pixel pipeline card in the traditional sense. I wonder how many people that bought this card actually know that. :laugh:

thay wont hav 32 pipes, coz 16 rops is definitely not enuf for 32 pipes

and apparently nvidia realised tht 16 rops arent the limiting factor as such for 24 pipes, dats y they decided not to increase it.

What GTX really needs is 512bit memory interface and faster ram - 1.4-1.6 gig

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Are you going to do performance benchmarks comparing all states? I'd be interested in seeing that in the next "part".
    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
  • Recent Achievements

    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      78
  • Tell a friend

    Love Neowin? Tell a friend!