SKU: 4079310146

Fabspeed IPD Y-Pipe - Porsche 991.2 Turbo/S

Sale price$721.35 Regular price$801.50
Save 10%

Shipping Estimate
USA
  • USA
  • CAN

Ships within 48 hours · Estimated delivery Jul 12 - Jul 17

Promo Codes Available:

For Your Every Summer RSVP, with Code: SUMMER15

Description

Fabspeed IPD Y-Pipe - Porsche 991.2 Turbo/SThe perfect compliments to Fabspeed's exhaust upgrades, this high performance intake plenum and y pipe from Innovative Pro Design provides substantial power gains by increasing the efficiency and flow of the engine's air intake system. IPD Y Pipe The new Turbo IPD Y Pipe delivers the same amazing proven performance as with the previous generation Turbo. Porsche made very few changes to the intake system from the 991 Turbo to the 991. 2 Turbo.

The perfect compliments to Fabspeed's exhaust upgrades, this high performance intake plenum and y-pipe from Innovative Pro Design provides substantial power gains by increasing the efficiency and flow of the engine's air intake system.

IPD Y-Pipe

The new Turbo IPD Y-Pipe delivers the same amazing proven performance as with the previous generation Turbo. Porsche made very few changes to the intake system from the 991 Turbo to the 991.2 Turbo. Ballistic acceleration and a top speed of over 200 mph places the new Turbo in a very elite class of supercars. But of course the IPD Y-Pipe (and Plenum) raise the performance bar even higher for Porsche driving enthusiasts who seek fighter jet performance from their German Turbo missiles. This superior design delivers greater volume of air, improved laminar flow and increased air velocity. These improvements deliver an additional 40+ wheel HP, 50+ Foot Pounds of Torque, improved boost response and more linear power and torque curves.

As we all know, bigger is not always better when it comes to forced induction applications. The IPD Y-Pipe is considerably larger than the factory but not so large as to cause pressure drop within the intake tract resulting in turbo lag and reduced performance. This optimized "no-round" design with dimpled interior surface cannot be achieved with conventional round tube construction.

The 991.2 Turbo Y-Pipe is a direct bolt-on engine upgrade that requires no modifications but should be perform by an experienced Porsche technician familiar with the 991 platform. Y-Pipes comes with all the required hardware necessary to complete the installation.

The 991.2 Turbo requires an "adaptation" period that can be fully realized with either a series of hard pulls on the dyno or a series of spirited driving sessions, which of course IPD recommends only be performed on a closed course circuit. Installation of all Turbo Plenums is highly recommended to be performed by qualified and trained Porsche technicians.

Features:
  • Superior and more efficient design over the factory intake
  • Deliver impressive power gains regardless of modifications
  • Produce substantial gains for both turbo and NA applications
  • Do not require an ECU flash and will not cause a CEL
  • Aluminum Plenums run cooler and don’t suffer from heat soak
  • All Fabspeed performance products are backed by the Fabspeed Lifetime Limited Warranty
  • NOTE: If you are upgrading your throttle body along with the IPD Plenum, you may need to visit a dealership to have them perform a manual throttle body adaptation process. Some customers have reported that installing the throttle body and plenum while the battery is disconnected results in the car performing an adaptation check once the battery is reconnected, alleviating the need to visit a dealership. However, Fabspeed recommends having the adaptation performed at a certified dealership for optimal results.
Shipping Notes
  • Free Standard Shipping on $100+ Orders to the USA.
  • Except Preorder products are shipped in 48 hours.
  • Delivery to the USA:
  1. Standard Shipping : 3-10 business days
  • If time is of the essence, please consider selecting expedited delivery for faster service.
Exchange/Return Notes
  • We offer a 30-day return/exchange service after receiving.
  • Final sale items are not eligible for returns or exchanges.
  • To process your return/exchange, please contact us at [email protected]
  • Please click here for more details>>> Return & Exchange Policy
SKU: 4079310146

Discover Niche Categories That Outsell

Top-Converting Item to Boost Your Average Order

4.5 ★★★★★
Based on 909 reviews
Sort
Highest Rating
Newest First
Oldest First
Product Reviews
C
Verified Purchase
cloud-learner
Draper, US
★★★★★ 3
have some good contents but too general
Format: Paperback
The book covers some good points, but overall, it's too general.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on June 28, 2024
E
Verified Purchase
Engineer Dude
Louisville, US
★★★★★ 3
Why Politics in a Tech Book????
Format: Kindle
Well... I'm surprised to see the book blatently calls out its dedication to Black Lives Matter, which is in all caps so I assume it's referring to the political organization. It goes on to speak of 2020 being the year of an "awakening of injustices of systematic racism"... I thought I was buying a technical book??? Had I known this political bs was included I wouldn't have purchased it! However, I bought and I'm still reading it. If the politics goes away and the TECHNICAL content is good I'll update my review.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on December 13, 2020
P
Verified Purchase
PeaceBee
Carnegie, US
★★★★★ 2
Not good use of time
Format: Paperback
It’s not clear who this book targets - neither experts nor novice will benefit. There are expert perspectives, only few of these are helpful, rest are too generic to be of any use. For instance the last entry is one an engineer who shares how she went from zero to expert in cloud engineering in six months but fails to mention a single resource or pathway for others to follow.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on April 2, 2022
N
Nilendu Misra
Omaha, US
★★★★★ 3
Uneven compendium of tips and insights, but still very useful
Format: Kindle, Format: Kindle
“In theory, theory and practice are the same. In practice, they are not" is why such bottom-up insights and lessons from the field are the fastest way to learn real life stuff. This series had a GREAT start with "Engineering Management" - I guess because it is way more subjective than Cloud Engineering and offered a variety of non-overlapping POVs. This one is a mixed bag, perhaps because "Cloud Engineering" was perceived amorphously by the authors. The scope was broad - from cloud-native (architecture), to cloud-ready (topology), to cloud-operations, to choosing tech (e.g., Lambda/serverless), to -ilities and economics -- it is like celebrating Halloween, Christmas and Labor Day together in a single long weekend. I would give it 4/+ stars if at least 25% of such a book was "superb", giving 3 because about 10% of the book is. That still leaves 10 solid insights or learning that would otherwise take many failures to learn. And failures, especially in this emerging domain of complexity, is VERY expensive. Would love to see more books like this. Let's summarize some key insights - -- Real-time visibility across the entire DevOps lifecycle is key to winning in cloud. -- Operations, especially operations at scale, is extremely hard. So, wherever possible, use Managed Services. -- Distinguish between "availability" and "uptime" and measure each separately, and concretely. -- In FaaS/Serverless, calling a function synchronously increases debugging complexity. -- Good code is like good joke - it needs no explanation. -- "Building your app or platform on top of the abstractions that a cloud provider gives you does not make the underlying layers stop existing. In many cases, it makes them even more important." That makes the failure modes LESS obvious than we were used to. Therefore having "extreme visibility" into your systems will help "separate the issues at the layer you're focused on from the fundamental system issues". i.e., just because what was under the hood is now even less visible, don't forget them. Many recent "cloud failures" have been in networking fault domains. -- Cloud is not optimized for replacing static infrastructures. -- Containers, service meshes and serverless jumpstart dev productivity but they also change the attack surface of apps and infra. -- "Number of containers that are alive for 10 sec or less has doubled to 22%". 73% of all containers live for 30 minutes or less. -- Adopt an "assume breach" stance for everything. Have a break-glass account. -- Ensure you have a thorough understanding of where and how secrets are secured. -- Grey failures (transient degradation of services) are often worse than complete crashes, since the latter have a short feedback loop. -- Resilience engineering has existed as a sub-discipline within safety sciences. We just recently started applying its concepts in technology. Resilience can be thought of as a "socio-technical system" with Robustness ("system X has property Y that is robust in sense Z to perturbation W"); Reliability (consistent operations or service levels); Rebound (ability to deal with a chaotic situation using structures developed AND deployed BEFORE the chaos). In other words, robustness protects systems against a SPECIFIC type of failure mode. When a system is robust in many dimensions, it approaches good resilience to failure. -- Resilience is something you "do", not something you "have". Resilience is a verb. -- Moving from one class of nines to the next is 10 times more expensive. -- Production System really means "system that someone else, anyone else, can hold you accountable for". -- Most common theme across incidents is that something, somewhere was surprising. -- Incidents are unplanned investments...your challenge is to maximize ROI. -- We used to think of scale in two dimensions - horizontal (more) and vertical (bigger). In cloud, think of "scale out" (when demands increase) and "scale in" (when demand decreases). -- Architecture diagram is also a map of failure modes. -- Async communication is a friend of Cloud Reliability. -- Test in production is a competitive advantage. The complexity of traffic patterns going through high-scale production systems is increasingly harder to reproduce in a controlled env. -- Hundreds of open issues is fine, but if the repo has gone months (or, years!) without a release, THAT is a warning sign. -- It is hard to write good tests for bad code. -- Platforms come and go. But first principles and patterns will always exist, because they are the ones and zeros.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on November 6, 2023
M
M. Klocker
Pawtucket, US
★★★★★ 2
Shallow, biased and significantly overpriced
Format: Paperback
Well, this purchase was a disappointment. 20% of the pages are dedicated to just highlighting the bios and backgrounds of the many different authors that contributed this great wisdom. And let me be clear, the authors are solid. They are professionals with credible backgrounds and experience. But it's the format and constraints of this book that makes it virtually impossible for that to shine through. Because the rest of the book (80%) is dedicated to the so called "97 things every cloud engineer should know". And unfortunately the average length of one of these "things" is about 1.5 pages long, and as such extremely shallow and in about 30% of the cases straight up promotions for specific company services. You will find Google cloud advocates telling you to use managed services, of Google of course. AWS engineers telling you to avoid them and use IaaS. LaunchDarkly employees telling you to use feature flags. The list goes on. The TL;DR: here is that if you have built anything on the cloud in the last 2 years, this book is going to be a waste of your time and money. You are better of googling: "cloud best practices" and dedicating 2h to reading the first 10 non-ad related search results.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on March 23, 2022

recommand products