Thanks Thomas for the introduction, thanks everyone for being here, hope you all had a good lunch, also welcome to everyone who's online, happy that you're able to participate as well. Like Thomas said, my name's David, this is my colleague Evan, we're both software engineers on the compute infrastructure team at Airbnb. We're going to be talking about how we moved, how our Kubernetes clusters have been evolving into heterogeneous clusters over the past several years. Quick outline of our presentation, Evan's going to talk a little bit about where we were before, give you some historical context on what our clusters looked like two, three, four years ago. And we're going to do a deep dive into three specific problems that we encountered. We encountered a lot more than three, but we picked three that we thought were sort of the most interesting. These are both sort of technical and organizational hurdles that we had to overcome on this journey. I guess the other thing I'll mention here is this journey is ongoing. Some of the stuff that we're talking about is done, some of it is in progress, some of it's not complete yet, but I think we've got a good plan at least. And then lastly, we're going to give you some future plans and lessons learned. The TLDR here is that heterogeneous clusters are great. They've already been instrumental for Airbnb and for our team. So with that, I'm going to hand it over to Evan to talk a little bit about some historical context. Great. Thanks, David. Yeah, as David mentioned, I'm going to start with a brief history of time of Kubernetes at Airbnb. In 2016 and 2017, we started evaluating Kubernetes for production use. Previously, we were running Chef on AWS EC2, where each replica of each service would have its own machine. In 2017 and 2018, we started building OneTouch, which is Airbnb's abstraction layer on top of Kubernetes for developers. The philosophy here is that all of a services config lives in one place in Git, and this config is then converted and applied as Kubernetes manifests to the cluster. In 2018 and 2019, there was a huge effort across our engineering org to migrate 90% of our 700 plus services at the time to Kubernetes. Our clusters were separated out by environment. So we had a prod cluster, a staging cluster, a dev cluster, et cetera. But this quickly grew out of hand as we hit Kubernetes single cluster node size limits, and we're forced to split these clusters into different cluster types. So we split our prod cluster into multiple prod clusters, our staging cluster into multiple staging clusters. And these clusters happen to be comprised of a single instance type. So single instance type clusters. This is what a single instance type cluster looks like. We have a pod come into a scheduler, and the scheduler tries to schedule the pod on a node with enough resources. Initially, we only had C5D9XLs as our node type because this happened to be the latest one we were using in EC2. And this was enough at first, but as more and more workloads started migrating, some specialized workloads required different instance types. So GPU workloads started migrating. We were forced to create a GPU cluster type, workloads requiring a lot of memory. We created a high memory cluster type for. And these cluster types were identical in both setup and config, and allowed us to expand them horizontally. Yeah, so why single instance type? This was before we had cluster autoscaler, which allows you to dynamically scale cluster size based on node capacity. Without this, multiple instance type clusters were not yet feasible. Any scheduling and capacity errors we ran into, we would have to resolve manually, which was quite a pain because we'd have to look at the different pod requirements and manually determine which node types would fit those scheduling constraints. Additionally, no cluster autoscaler means a lack of automation. We were at the time manually scaling all of our ASGs when we got alerted, which was not great. Yeah, so back to the timeline in 2019 and 2020. As more and more specialized workloads migrated, we had a cluster type explosion, and we went from around five clusters to over 90 that we have now, and we have over 30 cluster types. This leads to a lot of painful operational overhead for our team. Here's a screenshot of some 700, almost 700 alerts that we have just for ASG sizes, which really isn't great. This is our attempted solution to fix this, multiple instance type clusters, which look like this. We have the same thing as before where a pod comes into the scheduler, but this time the scheduler has many node types to choose from. It can schedule it on any node type that can fit the pod requirements of, in this case, the four that it has. But this time we also have cluster autoscaler, which handles the complexity of managing the ASG sizes, and it scales up the certain node types when required by a pod, but there's no capacity in the cluster. So yeah, why did we want to migrate? Well, first it brings our team quite a lot of quality of life improvements, reducing the number of cluster types to generalize clusters and make it so that we only have one process for cluster creation is really beneficial for our team, and it also reduces the number of alerts and alert fatigue. Secondly, we wanted to be able to control cluster composition at a global level. It unlocks some cost savings for us when we're able to utilize more node types rather than being locked into one, gives us some contract flexibility with AWS. In the future, we are trying to utilize spot instances so we can run part of our clusters on spot, and also new instance generation upgrades we get pretty much for free in the multi-cluster setting. Historically, this has taken us years to upgrade our entire fleet across new instance generations. Yeah, and the next section is solutions and other problems. I'm going to pass it back to David to talk about the first one. Thanks, Evan. So in this section, we're going to talk about three of the major technical and organizational hurdles that we had to overcome to do this migration to heterogeneous clusters. The first one I've entitled in which nobody knows what's going on. Specifically, this is going to be focusing on cluster autoscaler because it turns out that we didn't know what was going on with cluster autoscaler. When we started this process, one of the key questions that all of our stakeholders asked us is, how do we know what's going to be running in our cluster? Like, how do you know what mix of instance types you have? How do you know where things are going to get scheduled? And we thought we had the answer to that. So this first diagram here is not actually what happens, but it's what we thought happened. So a new pod comes in and KubeScheduler looks at the pod specifications, the resource requests, et cetera, and it's going to do one of two things. In the first case, which I'm calling the happy path, there's a node somewhere which meets all of the requirements and KubeScheduler just binds the pod to that node. I'm not going to talk about the happy path anymore. The unhappy path, there are no nodes in the cluster where the pod can run. And so KubeScheduler puts the pod into a pending state. It marks it as unschedulable. And cluster autoscaler then monitors the list of unschedulable pods. And it's going to try to spin up new EC2 instances that match the pod specifications. It looks at things like the resource requests. It looks at node selectors, node labels, looks at things like the pod topology spread, et cetera. It's going to iterate through all of the different node groups that it has, and it's going to select one that matches the pod specifications. And it's going to spin up a new host from that node group. So in our setting, node groups correspond exactly to ASGs. Because in a node group, you have to have all of the nodes identical. So they have to have the same CPUs. They have to have the same memory. This goes down to the labels and everything that are applied to nodes in that group as well. And so we have a different ASG that corresponds to each different instance type that we want available in our cluster. So anyways, once cluster autoscaler spins up that node, after it joins the cluster, KubeScheduler will then see, oh, look, there's a node that can accommodate my pod, and it binds the pod to the node. Nice and simple, right? Cluster autoscaler is making all these decisions about which node types to spin up, and we thought, great. We'll just hook into that process. It's not quite as simple as we thought. This diagram here shows what's actually going on. You can see that I've added a third middle path here, which I've entitled pause pods evicted. So what is a pause pod, you might be asking? Well, it turns out that for a variety of reasons, we want to be able to maintain additional overhead in our clusters. This is useful in the event that we have a spike in traffic, or we have some sort of an outage, and we need to fail over a service from one cluster to another. Having this overhead gives us the ability to handle those bursts in traffic seamlessly. The way that we maintain this overhead is through something called the cluster proportional autoscaler, which is different than the cluster autoscaler. What cluster proportional autoscaler does is it spins up pause pods. A pause pod is exactly what it sounds like. It just sits there on a node doing nothing, but it reserves that extra capacity. All of the pause pods are marked with a lower priority. So we've got our regular priorities, and then pause pods have a lower priority so that when a new pod comes in, cluster scheduler will look at that. It'll say, oh, here's a node that has a lower priority. It'll evict that one, and it'll make room for the new pod that just came in. We did a little bit of data analysis here and discovered that this middle path here is taken approximately 98% of the time in our clusters, which is great. It means that the proportional autoscaler is doing its job. We have enough capacity, 98% of the time, to handle our bursts in traffic. So what's the problem here? Well, in a single instance type world, the way that we configured things is we applied a instance type specific node selector to our pause pods. So that means that we're running C5D9X larges. Our pause pods could only spin up on C5D9X larges. This is for a variety of historical reasons, and when we moved to a multiple instance type world, this started causing us problems because then we'd create new pause pods for M5D, whatever instance types, and I'm sure you can see where this is going. When the new pod comes in, it evicts a pause pod and gets bound to the host where the pause pod used to be running. The pause pod then transitions into a pending state and cluster autoscaler says, aha, here's a pod that can't be scheduled. Let me try to spin something up to satisfy all of its requests. It has this instance type specific node selector on it, and there's only one node group that can satisfy that. So KubeScheduler doesn't know anything about different instance types. It doesn't know anything about ASGs or anything like that, it's more or less picking pause pods to evict at random, and what that means is that cluster autoscaler is entirely constrained in its choices by our pause pods. When a pause pod gets evicted, cluster autoscaler is forced to launch a new node that exactly matches that pause pod. So this was kind of a problem because it meant that we had all of these interacting control loops. We had cluster autoscaler, we had cluster proportional autoscaler, we had KubeScheduler, all of these things were in some sense fighting for control over our cluster composition, and this wasn't great. So what do we do about it? Well, in this slide, I show a slight modification to the previous slide. I'm gonna highlight the differences here. We ended up identifying two things that we could change. The first is that we moved away from these instance type specific pause pods to what I call generic pause pods. I'll explain that in a moment. And the second is that we built a custom expander plugin for cluster autoscaler. So let's dive into what each of those are. So as you might expect, the solution for pause pods is pretty straightforward. You just remove the instance type specific node selector. So now we have what we call generic pause pods. They can run anywhere. This is great. In terms of sizing, previously we had the pause pod just take up the entire node. Now we're going to size the pause pods to be the smallest of the instance types in our cluster. So if we've got node types that have 32 CPUs and we've got node types that have 64 CPUs, we'll size the pause pods to request 32 CPUs. This means that, well, maybe a bigger node might have multiple pause pods running on it, but that's fine. We can tweak our overhead parameters to accommodate that. Now the only sort of remaining concern here is what do we do about our SLAs around scheduling? As you recall before, 98% of the time we're evicting these pause pods in order to make room for new workloads that are coming in. And what that meant is that most of the time our services are getting scheduled in one to two seconds. And we really wanted to make sure that as we move into this multiple instance type world that we're able to maintain that. And this becomes a problem if we start consolidating like our GPU clusters or some high memory workloads. We try to mash all of those different things into a single cluster while you might have a job that comes along that's requesting 500 gigs of RAM and our pause pods, none of them request 500 gigs of RAM. And so it might have to wait, that job might have to wait five minutes or 10 minutes or however long it takes for a new node to come up and join the cluster. And this could be a regression in performance. So the solution that we've identified, this is a piece that we haven't implemented yet is that for jobs like GPU workloads or high memory workloads, we're gonna build in a shadow capacity mechanism so that if you've got a specific service that has unusual resource request, essentially you're gonna get pause pods that are specific to that service so that you can maintain those scheduling guarantees. All right, so let's move on to the second piece that we are introducing. This is our custom expander plugin. This is in progress. We have a really basic proof of concept right now, but we expect this is gonna get a lot more complex in the future. What we observed is that cluster auto scaler is performing a lot of common tasks and we really wanna keep all of that functionality in cluster auto scaler does things like talk to the cloud provider. It runs this simulation where it determines all of the different places that a pod could go and does a lot of really nice things for us. What it doesn't do necessarily is capture the business logic that we want to determine what node types to spin up. So how does cluster auto scaler actually pick a node type to spin up? Well, first it does this filtering step where it identifies all of the node groups that potentially could run the incoming pod. Then it passes those node groups off to what it calls an expander. There are a number of expanders that are built in. There's one that's just the random expander. It's gonna pick one of those node groups at random. The one that we use right now is called the priority expander. So you rank all of your node groups by priority and it picks the highest available priority. It's got a few others, but what we predict and what we're already seeing is that we're gonna want even more control over the node groups that get selected. What we didn't wanna have to happen is that we maintain a fork of cluster auto scaler that has all of this business logic. We want it to be good CNCF citizens and be able to contribute some stuff back upstream and we also want it to make our lives easier. And it turns out that I think with this custom expander plugin we can do all three of those things. So what we're gonna do is patch cluster auto scaler so that it can communicate over GRPC with a separate process. And that separate process is gonna encode all of our expander logic. It's gonna be all of the business logic around what instance types we currently want to run. As Evan mentioned, we wanna start dipping our toes in the spot world. And so this custom expander can do things like look at all of the prices for all of the spot markets that we're in and let's maybe pick one that's cheap right now or that we think has a lot of availability. It can do things like, well, we've got a whole bunch of batch jobs that are gonna be requesting a bunch of memory. So maybe for like bin packing reasons we should request some instances that have more memory or something like that. All of that business logic can get encoded in this expander that is separate from cluster auto scaler itself. This is nice for a couple of reasons. It means that, A, we're not maintaining a fork of cluster auto scaler and B, we can upgrade the two out of band. We don't have to, if our AWS contract changes and we need to fix some of that business logic we don't have to deploy a new version of cluster auto scaler. We can just deploy a new version of this service that we're running. So like I mentioned, this is in progress. We have a work in progress PR that I'll link at the end for this expander. But this is going to really be where we control the composition of our clusters. So that I'm gonna hand it over to Evan to talk a little bit more about some of the organizational issues we've encountered. Yep. Thanks, David. Yeah, so David covered some of the technical issues. This section will be a bit more around the organizational issues. This chapter is titled in which customers are concerned. So because we're coming from single instance clusters service owners had the expectation of identical pod performance across different machines. Another issue we thought of was that our service owners have a lot of migration fatigue. We currently have nearly 1,000 services and with every infrastructure config change leads to migration and every migration causes wastes a lot of engineering time. Our first solution here was talking to people. We sent out surveys and talked with a lot of customer teams. We realized here there were actually quite a lot of nebulous concerns around performance without the teams knowing exactly what requirements they had for their service around performance and most of them hadn't really done any performance testing or performance tuning either. They only came to us with sort of like relative comparisons to their current performance, whatever that performance may be. Out of these talks we created an extensible API out of which was kind of twofold. It allows customers to specify specific instance types if their workloads are actually super sensitive to the different underlying node types. And it is also opt-in, which solves the default is opted in, meaning service owners would have to opt out. This solves a lot of the migration issues because we expect this to work for almost all services. It also allows for additive requirements when service owners are describing the instance types they want and is therefore extensible for our future work, like I said before, like utilizing spot instances and others. To try to address customer concerns, we did a bit of performance testing for these new instance types. We started with running some benchmark tests. So we ran a variety of Sysbench synthetic tests and found performance between the instance types to be within 20%. But obviously this isn't good enough for production workloads. We needed to use real workloads to test this. So we took services test environments with production traffic replay, scheduled them onto different empty nodes of all the instance types we were testing to compare the latency metrics. And we did this for a representative set of service profiles that we have. This was across different languages, so like Java, Ruby, and Node, latency requirements, SLOs, and across different workload types.  Here's an example of a very latency sensitive service that we have. The different colors here, orange and purple represents the different instance types and each grouping is the P95 and P99 of the latencies. You can see they're like really, really similar. We have actually found this to be the case for all of our services and all endpoints. We found that performance was within 10%, which we deemed acceptable enough to move forward. And yeah, so as we started rollout, we found quite a number of very, very technical issues with cluster autoscaler. We don't have time to cover them all in this presentation but we'll deep dive on one of them and then link the bug fixes and issues we filed upstream at the end. And I believe these slides are uploaded so y'all can take a look if you're interested. So yeah, the problem we saw was that during our rollout, we observed that certain ASGs weren't launching. This was kind of strange because the logs, when we checked them, showed pod topology spread failures. If you're not familiar, pod topology spread, all it does is guarantee that pods are spread evenly across availability zones. Here's a screenshot of the logs. You can see, if that's not too small, that the M5D12XLASGs in US East 1B fails pod topology spread constraints and then later on in the logs, the C5AD12XL in the same zone ends up succeeding and being chosen to scale up. This is really weird because it's exactly the opposite of what pod topology spread is trying to do. And then this graph shows our gradual introduction of these new instance types to one of our clusters. You can see these C5AD12XLs in the top in blue gradually taking up a larger and larger proportion during our rollout. But C5AD16XLs and M5Ds aren't launching at all. So after a while, we realized that the ASGs that weren't launching were empty ASGs. In this case, it was the M5D ones and the C5AD16XLs. And this was kind of strange to us because both of those ASGs happened to be the very top priority in our expander ladder. And we'd expect them to launch before the other ones. So this was kind of strange. We did quite a lot of code digging and we learned a couple of things about cluster autoscaler. So what's going on? We have a cluster here with the four ASGs, two of which are populated, the C5D18XLs and the C5AD12XLs. And then the two on the right are empty.  Cluster autoscaler undergoes a scheduling simulation when this happens and looks at possible node types to expand and sees if the node types will fit the scheduling requirements of the incoming pod. So how does this scheduling simulation work when evaluating if a pod will fit? Well, it looks at the available node types it has, in this case, the four on the bottom. And it creates these fake nodes that populate node info objects for each type of node and it sees if this fake node will fit the scheduling constraint. But that begs the question, how does it populate this node info object? Well, it turns out there are two paths for ASGs that have live nodes in the cluster. It copies the node info directly from existing nodes. In this case, the two on the left. But for the ones that are empty, we have these things called ASG templates, which whenever cluster autoscaler chooses to launch a new node, it takes this ASG template, which describes the node config before Kubelet starts on a node. This seems fine, right? But I mean, in most cases it is fine, but Kubelet actually applies quite a lot of labels and annotations to a node on startup, including architecture, OS, the host name, the instance type name. But then most importantly for this scenario, the topology key, topology zone key, this means that ASG templates don't have that topology zone key, which explain the behavior we were seeing because the fake nodes that were copied from the ASG templates don't have the topology zone key. The ones from the existing nodes do have that key because Kubelet has already started on those existing nodes. And thus we see our behavior in the logs where the existing nodes, even though it's a lower priority than the other ones that were empty, is chosen. Our short-term fix for this is to just manually add the topology zone key to the ASG template. This is pretty counter-intuitive behavior because you wouldn't expect to have to add that because Kubelet does it for you. The long-term fix here is to modify cluster autoscaler to automatically add all of those Kubelet tags to the ASG templates when it's evaluating. Yeah, so David, do you want to talk about what we learned? Sure, thanks. So let's see, what did we learn? Testing, there we go. Cool, yeah, sorry about that. Thanks, Evan. What did we learn from this whole process? Well, the short summary is that heterogeneous clusters are really great. We should do more of those. But you might be asking what's so great about them. Well, I think the biggest benefit that we've gotten from all of the work that we've done so far, we're still kind of in a half-finished state and we're already seeing this benefit is it gives us a huge amount of flexibility in our team. We've gone from, as Evan mentioned, like taking years to migrate from older generations to the VC2 instances onto the most recent ones to being able to do that with a single config change in a couple of hours. Even earlier this year, it took several weeks to even just be able to add a new instance type into our cluster. And again, that's now a couple-hour task at most. So it gives us a huge amount of flexibility to respond to changes in our demands, in the cloud provider markets, you name it. We can now handle all of these different changes without really overburdening our team. So that's great. Second benefit is also this allows us to future-proof our systems a lot more. And this really boils down to just being able to add new instance types as AWS makes those available. The third thing is really around cost. Historically, we just picked an instance type and went with it, because that seemed like the thing to do. Now we can actually critically analyze are we getting the most bang for our buck with the instance types that we have in our cluster. Evan and I have hinted several times that we wanna also start incorporating spot instances and all kinds of other stuff. We're investigating AMD, we're investigating Graviton, all of these different things. We're now going to have the capability to make these trade-off decisions where we wouldn't be able to do that before. So what's next? We still have a number of changes to cluster autoscaler that we're trying to get upstreamed. I'll have a list of those on the next slide. We're still in the process of rolling this out as well. Like I mentioned, some of these things are still in progress. We only have a handful of our 50, 60-odd clusters running in a multi-instance type setting right now. So we wanna roll this out to the rest of Airbnb. And then our next big project after that is running on spot instances. This was really a prerequisite to that. And yeah, so this is a list of existing PRs and issues that we filed against cluster autoscaler. These are on the slides that are uploaded. I think there's gonna be like one or two more that are coming that we just discovered in the last couple of weeks. And with that, I think I will conclude. I wanna thank everybody again for attending. I'm happy to take any questions or Evan, any questions that you all have and just wanna put out a shameless plug that we are hiring. So if any of this stuff sounds interesting to work on, you can come talk to us after the presentation. So thanks very much.


What goes through the narcissist's mind when he idealizes you? What goes through the psychopaths mind when he discards you? And what goes through the borderline's mind when she alternates and vacillates and oscillates and every other leads? between her various dysregulated labile self-states How does it feel to be inside? The abuser's mind Now there are quite a few self-proclaimed narcissists Who try to verbalize their inner experience some of them even do it honestly? And there are quite a few victims real ones self-styled professional ones And covert narcissists posing to be victims posing as victims and all of them try somehow to get a handle to grasp the inner landscape of The narcissist the psychopath and to a lesser extent the borderline I'm saying to a lesser extent the borderline because the borderline is much more human than the narcissist let alone the psychopath the thing is that in the absence of empathy and access to emotions narcissists and psychopaths are not fully human in Any true sense of the word no amount of empathy can help you what is needed is scholarship And so this video is based on studies published papers academic journals articles and The decades-long work of luminaries From let's say Kernberg cohort Theodore millen All the way down to twinge all the way up if you wish to twinge and Campbell To this I can add my own personal experience and the fact that I have a date database of 1783 true to this morning Diagnosed Narcissist and psychopaths people diagnosed officially With narcissistic personality disorder and antisocial personality disorder by professionals and diagnosticians not by their own spouses or angry neighbors or colleagues And in this database of 1783 individuals They responded to a structured questionnaire with 683 questions If you multiply the two you get an overwhelming database Regarding the what it means.  So today I'm going to discuss the narcissist How does he experience you? Not the other way So first of all, it's it's critical to make a distinction between narcissists and psychopaths. This distinction is often lost online by self-styled experts and others and they often confuse Irredimibly confused narcissists and psychopaths they attribute to narcissists many things which are actually the domain of psychopathy and They very often attribute to psychopaths many behaviors which are exclusive to narcissists It is true that every psychopath has a pronounced streak of grandiosity And it is true that some narcissists the small minority are psychopathic narcissists They are antisocial defined Like impulse control and so on, but that's a tiny tiny group. They used to be known as malignant narcissists In today's video, I'm going to discuss the classic narcissists the overt Classic narcissists not a covert not a malignant which are tiny minorities But they run of the mill Pedestrian narcissists that you're very likely to come across because anywhere between One percent one and a half percent and six percent of the population depending on which study you believe which study you trust our narcissists people with pronounced narcissistic traits behaviors style and personality So these are the narcissists you're going to come across Similarly, when I'm when I will discuss psychopaths a bit later. I'm going to discuss the typical psychopath Not the serial killer Most serial killers are sexual sadists and also psychopaths, but they're rare Luckily, there are few of them, you know, so it's a bit pointless to meet To to create this melange or cocktail of all these types because it's very misleading and very confusing So let's start with the narcissists For you as a as a victim or a potential victim or a survivor or Someone who might come across a narcissist in your daily life in the workplace in a romantic setting on a dating app For you, it's critical to understand it as far as the Nazis is concerned. There is no distinction between his fantasy life and real life He has impaired reality testing.  They confuse exactly like psychotics They confuse inner objects with outer external objects. I You're all acquainted by now. I hope with the famous mechanism of snapshotting Where they interact with a snapshot of you they take a snapshot of you and then they interact with it With your representation with your avatar with your intro jack not with you and So what they do they internalize external objects, especially significant objects And especially objects that they can cause them pain and so they by abandoning them So they internalize these objects and then they continue to interact with the internal representations within a shared fantastic space and They can't tell the difference This is why they miss label emotions Narcissists feel intense emotions many many scholars Speculated that perhaps narcissism is in psychopathy are our reactions Defensive reactions defensive attempts to avoid very very deep Emotionality Perhaps narcissists and psychopaths or at least narcissists emote too much too strongly too intensely They are about to be to be overwhelmed by their emotions So they isolate themselves from their emotions. They put a firewall They put a mode and a fence and a fortress a fortification to avoid their emotions And this is why Rothstein and other scholars suggest that borderlines people with borderline personality disorders Are people who had tried to become narcissists and faith? These people are overwhelmed by dysregulated emotions These people drown in their emotions like COVID-19 emotional COVID-19 They drown in their own emotions because they can't control these emotions These emotions are much stronger than they are and they don't have a narcissistic defense So narcissists are capable of intense emotions the thing is that They feel them the experience the emotion, but they don't know what it is Because they are divorced from reality and they have this cognitive deficit and impaired reality testing They ask themselves What am I feeling now? What is it that I'm feeling now? Oh Must be love. So they say well, I love you They mislabel or they say I must be angry Narcissists Experience their emotions through a cognitive analytical filter They have to ask themselves What they're feeling and then they compare their experiences their reactions their moods their affect Their behaviors they compare all this to an internal database The database where they have entries and listings for how people behave when How people behave when they are sad they cry I cry therefore I'm sad How people behave when they're happy they smile I'm smiling now therefore I must be happy How people behave when they're in love? They crave the presence of the loved one. I crave the presence of my intimate partner. So probably I love her Of course the narcissist craves the presence of his name intimate partner because she gives him supply but he he even if he's aware of what supply is and Most narcissists by the way are self-aware. It's another idiotic myth online that they are not most of them are They're just proud of their disorder, but they are self-aware Self-aware, but mislabel Self-aware, but get it wrong Self-aware, but don't understand what they are aware of So Very often they think they're in love And they embed this love in the shirt find this perception of love misperception of love in in a shirt fantasy It's fantastic love because everything in the narcissist life has to be bigger than life Has to be fantastic has to be amazing has to be perfect has to be brilliant has to be everything is grandiose so the love must be grandiose and There is a difference between the shirt fantasy of a narcissist and the shirts fantasy of a psychopath I'm reading books where there is God almighty confusion between the two The shirt fantasy of a narcissist Involves imperfect mirror in other words the shirt fantasy of a narcissist Survives differences between the parties survives friction Survive this agreement and criticism and so this punishment, but it survives these things The shirt fantasy of a psychopath is perfect mirroring the psychopath doesn't live Doesn't leave Daylight between himself and his target The psychopath emulates and imitates the target to perfection So that the target feels that she had found her soulmate her twin her doppelganger her other The one she's been searching for all her life in other words herself So while narcissistic mirroring Idealizes the partner Allowing her to fall in love with her idealized image Psychopathic mirroring Includes idealization, of course plus the added element of Identity between the psychopath and his newfound so-called Love or intimate partner and the victims of psychopaths fall for it They feel that they had found the perfect resonance that they had been looking for all their lives This is rare with a narcissist What the victims of narcissistic feel is that they had found someone Who makes them feel good about themselves at the beginning at least and the shirt fantasy is established both types love bomb But usually only the psychopath grooms and When the shared fantasy is a psychopathic shared fantasy And it is it reaches its natural end its expiry Many psychopaths become long-term stalkers before they finally let go if they do Contra to information online It is the narcissist Who would let go of a shirt fantasy and move on to another target the famous idealized the value? discard replace is A narcissistic strategy because the narcissist is in need of a shirt fantasy all the time He cannot survive a minute without a shirt fantasy. So he immediately Replaces a defunct a dead Then expired shared fantasy with a new one The psychopath is different the psychopath is goal oriented will come to it in a minute And when he shared fantasy goes down the drain he won't accept it He won't accept it and many of them become long-term stalkers And this is regardless of whether the fantasy was active or not In other words regardless if there was a relationship at all Or whether it was all in the psychopaths head In the case of the narcissists Some narcissists become stalkers, but they become stalkers within an active Shirt psychos a shirt fantasy in other words narcissists talk Only as long as the partner gives them hope For example as long as the partner remains physically Cohabits with them doesn't leave home as long as a partner keeps calling them may communicating with them as Long as the partner keeps dropping hints that you know so as long as the shirt fantasy is active The narcissists will stalk Will stalk the target that is the process of hovering in effect The psychopath will stalk even after the shirt fantasy is dead as far as the other as far as the partner is concerned Because it's psychopaths Psychopaths are defined It's my way or the highway. I will decide when the shirt fantasy is over not you Narcissist is different Narcissist says as long as you give me hope I will be after you I'll keep coming keep coming back for more keep trying to coerce you to convince you to return to the shirt fantasy but the minute The narcissists is truly modified Get through his his thick skull that it's over He has to move on with the liquidity with speed as you cannot survive a second without a shirt cycles a shirt fantasy Within the shirt fantasy There's another difference The narcissists in the shirt fantasy Because the fantasy for him is a reality He misjudges the nature of the relationship Exactly like the histrionic he misjudges the intensity the depth the intimacy the commitment of the other party the motives of the other party Lies that he is being told he believes because he becomes Sudo stupid he becomes gullible within the shirt fantasy so He misjudges the nature of their relationship the nature of the shirt fantasy But he never misjudges the existence of the shirt fantasy. In other words after modification becomes clear to him the fantasy is dead The psychopath is exactly the opposite Psychopath never misjudges the nature of the shirt fantasy because he creates it as a tool to manipulate He's goal oriented or she's gone or it He creates a shirt fantasy because within the shirt fantasy you can get what he wants Sex power money contacts these that access Psychopath is everything creates a simulation creates a matrix Within which his victims react exactly as they want them to react and further his aims and goals So he never mistakes the nature of what's happening, but he sometimes mistakes The existence of the fantasy exactly opposite of the Nazis He won't he won't take no for an answer And this is why psychopaths are very very dangerous much more dangerous as intimate partners than Nazis The Nazis is Operates on kind of two tracks. He has a two track mind It's easier for the Nazis is to operate to two tracks because the Nazis is essentially is a broken personality I even suggested many times the Nazis has multiple personality. He has a true self and a false self by definition So it's a form of dissociated by the entity disorder Nazis is dissociated a lot. They depersonalized today realize they have dissociative amnesia exactly like border lines It's easier for narcissists to work on two tracks and within the shirt fantasy the narcissists works on two tracks there is this Guy if you wish this entity this locus Which is rarely wrong? clear-eyed insightful intuitive and a lytical Prognostic prognosticator. It's almost I would say supernatural telepathic the narcissist knows at every given moment when he's about to be betrayed for example and at the same time At the very same time concurrently There is a child there Deluded caught in the fantasy erotomaniac kind of kind of Dependent with an impaired reality test with a confirmation bias filters out Information that is hurtful countervailing This second entity is always shocked when He's cheated on or betrayed in another way The former entity communicates with his partners the latter entity the deluded child communicates with him the former entity Is the one that interfaces with the with the women but the latter entity is The one that captivates the partner So even in the partner there's a similar duality Similar break which explains the unease when you're with the narcissist Do you feel that it's sometimes you're communicating with a very hurt very small child and at other times with a pretty sharp cookie with a tough tough as nails lawyer type Who is you know won't take bullshit won't take no want won't buy your stories and lies and everything Sees through you It's very penetrating in every way so This is the duality of the of the narcissists. There's no such thing as a psychopath With a psychopath What you see is who you are There is no one there the psychopath is a perfect mirror The narcissist provides you with a whole of mirrors Which reflect these mirrors reflect you wrongly by idealizing The narcissist provides you with a whole of mirrors Which reflects you totally the emphasis is on totally not not so much on idealizing you But on being like you being identical to you So while the narcissist will tell you for example That you're good-hearted because it's part of the idealization the psychopath may tell you that you're actually pretty vicious Exactly like him You're vicious and vicious. We are one of the same. We're the same person The psychopath messages. We are one organism. We are one entity with two heads It's a merger infusion message.  I'm you You positive and negative This is not the narcissist message the nicest is messages.    It's a way to idealize yourself as an arsonist way to buttress your grandiosity This process is called co-idealization. It does not happen with psychopaths Psychopaths are not interested at all in narcissistic supply their grandiosity the psychopaths grandiosity is inward-looking it's it's Self-sufficient it's self-contained The psychopath knows that he's superior end of story doesn't need anyone to confirm it to him He just knows it. It's a fact in this beautiful fact. Who can who can argue with that? Who can argue with it?  He's very easy to destabilize is is very uncertain There's an external locus of control and so Then the psychopath does not co-idealize When and if the psychopath idealizes you it's part of a process of manipulating you subjugating you Rendering you addicted to his praise. It's it's goal oriented. It's a tool. It's an instrument. It has no reflection on him Psychopath is utterly unaffected by his idealization of you I Mean who cares what you are really and who you are really What is it? What is all matter? It's like, you know me and me Co-idealization the narcissist co-idealization occurs simultaneously in two spaces One space is real one is imaginary. This is not the case with the psychopath The narcissist pathological narcissistic space is his stooping ground. It's a real space. It's a physical space Could be his home church neighborhood pub volunteer organization or workplace It's a location. It's a location in which his sources of supply habitually congregate and interact to provide the narcissists with adulation and affirmation Applause. No, it's where he get applause. So it could be a concert hall And concurrent with this physical site the narcissist maintains a shared fantasy space here in his mind and Within this shared fantasy space. He idealizes both himself and and his intimate mate Co-idealization psychopath doesn't have this psychopath has only a Space a single space and it's a totally physical space The psychopath does not have a shared fantasy with you.  He creates a fantasy space for you a Disneyland mental Disneyland, but he never Never makes the mistake of confusing this space that he had created his work of art with reality like the narcissist does So the psychopath is only physical locations or digital Communication which is also physical because you have to hold the smartphone. It's very nice. The psychopath is very reality based It doesn't have an impaired reality test.   So he ignores reality because of his grandiosity But he never mistakes it for a fantasy not so the Nazis is Nazis is much more psychotic Much more psychotic than the psychopath And I beg to differ with Kernberg and others much more psychotic than the borderline When the narcissist is forced to return to reality when he's brutally awakened and Decompensates when his defenses crumble fall apart He usually does it Come comes back to reality wake wakes up by by having been narcissistically injured or even modified It's a precondition The Nazis never abandons the fantasy Because it sees reality when he is expelled from the garden of eight of Eden When he's expelled from the garden of Eden, there should be an angel there with a flaming sword or else He will try to re enter the garden and eat another apple with a naked Eve. I Love this imagery. Okay so The Nazis is not statistically injured. It's mortified and then what he does he devalues The fount of hurt and frustration. He devalues the source if I was a person who hurt him who frustrated him Usually it's the intimate public, but it doesn't have to be What he uses the infantile Splitting defense mechanism. You remember what is splitting black and white good and bad good and evil Right and wrong.  We call it decotonous thinking Black or white thinking all or nothing all or nothing thinking so he uses this infantile splitting defense to render his partner the polar opposite of her erstwhile Idealized version So if she were if she were in the idealized version dropped it gorgeous. No, she's getting old if she were a genius now She's either a genius only in certain things or really very stupid but Exactly as idealizing the partner resulted in self idealization. You remember call idealization like he idealized the part of idealize himself So it's tense reason That devaluing the partner should result in self devaluation and Narcissus go through this phase. They ask themselves How could I have been so stupid and blind and gullible and wrong and fallible to not see how inferior she is and This is a phase That is common to narcissists and to victims of narcissists ironically. Don't forget Narcissus are the outcome of narcissistic abuse in early childhood. They are Post-traumatized they're in a post-traumatic condition. I Even suggested that narcissism is not a personality disorder, but a post-traumatic state So they have exactly the same reactions like the victim of narcissistic abuse but Infused tinged imbued painted over with grandiosity And to avoid this excruciating outcome of saying to himself I've been stupid. I've been wrong I've been to avoid this excruciating outcome to avoid this Inner internally generated challenge to his grandiosity The narcissist engenders an external Modification you remember when in the four videos where we analyze where I analyze modification. I told you that modification The one of the ways to cope with modification is to replace it with another modification, which is much more acceptable So the narcissist creates another modification, which is more acceptable to him. This modification says she is evil She's dumb.  Remember fantasy is his reality When he's taken out of the fantasy, he feels the same way you feel When you are caught in a nightmare It's exactly Narciss world is a mirror image of your world What to you is reality to him is fantasy and what to you is fantasy to him is reality So when he's when he's forced to confront reality as it is He feels he's caught in a nightmare from which he cannot wake up Except through the good services of a new intimate power And now let's transition to the psychopath Contrary to the narcissist the psychopath has no emotions None end of story Narcissists have emotions They are terrified of their own emotions.   It's a walking talking simulation of a human being It's a brilliant wonderful amazing simulation so it can convince you that it has empathy his emotions His healing is changing is it's it's a wonderful rendition of A perfect human being and it is this perfection That it is that is the first sign of trouble If he's too good to be true, he's a psychopath and There are two types of psychopath essentially. There's a mischievous psychopath. I Call it the clickly psychopath after Harvey clickly the father of the study of psychopathy together with carpman So the mischievous psychopath I Think has affinity with the secondary psychopath the secondary psychopath is capable of some rudimentary conscience empathy and emotions some a little and The secondary psychopath is about entertainment. He is focused on having fun Entertaining himself he's bored all the time.     So he tells you stories exactly like the narcissist Exactly like the narcissist who wants to engender a shared fantasy Psychopath also would lie to you. I don't know promise you love A romantic affair marriage a business partnership The second type of psychopath is goal oriented. I call it the hair psychopath or the baby egg psychopath after the two scholars who Dedicated their lives to studying this kind of circle the goal oriented psychopath also known as the primary psychopath He's wrong. He's a he's goal oriented. They say the name implies so he wants something I don't know sex. He wants money wants access. He wants your contacts. He wants your address book He wants he wants to have he wants to team up with your friend not with you But he needs to go through you. He wants to get something from your father But he needs to pretend that he's your lover so that your father gives him money He has something in mind. He always has something in mind.  He wants to use you. He wants to exploit you And now I come to the borderline borderline is a very complex disorder It's a complex miss disorder because it has elements borrowed from Other cluster B personality disorders. It has the narcissist's grandiosity. It has the psychopath's defiance and lack of impulse control it has object inconsistency it has defense mechanisms which are typical of narcissists it has histrionic behavior For example hyper-emotionality Misjudging the nature and depth of intimacy and relationships. So borderline is a kind of amalgam cocktail Precy Dictionary encyclopedia of all other cluster B personality disorders, but coupled with Coupled with elements which are typical of other clusters For example seriously dysregulated emotions Moodle ability which very often imitates bipolar disorder. It's not but imitates bipolar disorder Irrassibility and rage Which are typical of some schizophrenics and paranoics the borderline in this sense Is not a real clinical entity That's why when we look at borderlines We can divide them into types and subtypes and sub-subtypes and species and sub-sub-species it endlessly to the end to doomsday because Each borderline has their own disorder. It's a little like You take a woman most borderlines a whip you take a woman and tell her okay Go through the DSM and pick up you know as many traits characters characteristics and behaviors as you wish from any disorder that you want So no no borderline is identical to the other Not one is identical to the other It's it's like if there's for example a hundred million borderlines then there's a hundred million Types of borderline personality disorder makes it extremely difficult For their intimate partners to cope with them To live with them to anticipate them to manage them to manage a relationship to communicate with them Very difficult Still of course all borderlines have a few things they share in common and and within today's Presentation what is important to understand it is that the borderline transitions Cycles there's a borderline cycle she Encounters some problem if frustration a real rejection and you imagined rejection and humiliation And abuse she's been abused or she thinks she's been abused a lot of Borderline borderline exactly like the narcissist has an impaired reality test and magical thinking So everything that happens in her head is actually reality. I mean if if you think it must be so and so Whenever I say rejection or humiliation or abuse or withholding or it could be real and could be imaginary or anticipated it She predicts it's gonna happen And so she reacts to frustration Not with aggression There is a classic hypothesis in 1939 by Donald that Frustration breeds aggression. It's true generally the borderline is a bit different initially She reacts to aggression by becoming a narcissist She has grandiose by becoming simultaneously. I'm sorry a narcissist and a secondary cycle simultaneously, it's extremely Unsettling to watch I've had the privilege Of the misfortune of watching quite a few borderlines go through this. It's it resembles To a very high degree The switching between personalities in someone with multiple personality disorder And that's why many many scholars suggest that borderline personality disorder is a dissociative identity disorder is a dissociative State so that the borderline has many self states. They are not personalities. They are not that well developed But they are distinguishable And if you ever saw borderline Faced with frustration For example rejection or withholding or being ignored being abused You can see When you watch her you can see her changing Metamorphosizing shape-shifting and Then she kind of splits. There's a part of her that becomes a narcissist and the second part becomes a secondary cycle So as a narcissist, she would suddenly become very grandiose With impaired reality testing Disempathic borderlines are usually empathic, but she would become then disempathic Vicious in them and then as a secondary psychopath, she will be cold and calculated She would think how to hurt how to arm How to cause pain she will become even a bit sadistic She will be defined She would have no impulse control She would not consider the consequences of her actions.  It's very easy to manipulate it And what the Nazis is in her is a soulmate She's equally grandiose and she knows how to gratify him because she is also a narcissist in some ways and so Borderline is very likely exactly like the codependent by the way these two types are very likely to agree willingly and lovingly and eagerly to participate in the narcissist shared fantasy and To submit themselves to a psychopath a primary cycle The borderline feels safe with a primary psychopath because she has the personal experience of What it means to be a psychopath? As a secondary psychopath She feels strong. She feels empowered. She feels in control She feels that she has the power to inflict pain rather than experience pain She feels she can dysregulate other people situations So the primary psychopath is like her is what what she wants to be when she grows up is like an idol a Rockstar a the ideal that she aspires to in many ways Makes her feel safe and protected and understood and taken to a new extreme or a new level elevated very often we find a mom for example Couples who are serial killers we find one borderline among ones primary psychopath And on the other hand she's also open to participate in the shared fantasy of the narcissist The narcissist idealized idealizes his intimate partner and caters to the borderline's Grandiosity, which is her main and only defense against dysregulation Lobility in utterly intolerable tolerable and bearable pain which drives close to 11% of borderlines to commit suicide So borderline finds both of them Irresistible because both of them truly are her soulmates My name is Santak me and I'm the author of Malignant self love narcissism revisited One last comment Many of you women of course wrote to me. I never cheated on my husband I never dreamt of cheating on my husband. The thought never crossed my mind Allow me to disbelief a lot of this But let's assume I believe you you should really really watch videos much more carefully. I Made very clear in my previous video then I'm giving cheating as an example of Cause for mortification. I even mentioned explicitly that it doesn't have to be cheating It could be absconding with the family's money. It can be other reckless behaviors. I don't know and bridal chopping Gambling of a logical gambling or just packing up your things and disappearing which is an aggressive aggressive Disregulated act. I mean, there are many ways to modify a narcissist one of the most common ways is cheating and because Nazis profess profess to be Maximally mortified by cheating. I took that as an example an idealized example, but ladies Please listen well Before you make comments Thank you


What's going on and welcome to the solo shot? My name is Tom Vecchio. We have an 11-game MLB slate lock is set for 705. As always, this is one of the many shows on the Feindle Podcast Network. You can find that anywhere, whether it's on Apple Podcasts, whether it's on Spotify. The video version can be found on the Feindle YouTube page. You can also be found on Feindle TV Plus and feindle.com slash watch. You can follow me on Twitter at Tom underscore Vecchio 1. Before we hop into things, get ready for the NFL season with incredible offers from Feindle, America's number one sportsbook. Right now, new customers can bet $5 and get $200 in bonus bets guaranteed. Plus, all customers who bet $5 will get $100 off NFL Sunday ticket from YouTube and YouTube TV. Now is the best time to join Feindle. The app is easy to use and you can bet on everything from spreads to player props and more. Feindle official partner of the NFL must be 21 plus and present in select states. Feindle is offering online sports wagering in Kansas under agreement with Kansas Star Casino LLC. First online real money wager only $10 first deposit required. Bonus issued as non withdrawable bonus bets that expire seven days after a seat. Restrictions apply. See terms at sportsbook.feindle.com. Game and problem call 1-800-Gambler or visit feindle.com slash RG. If you're in Colorado, Iowa, Michigan, New Jersey, Ohio, Pennsylvania, Illinois, Tennessee or Virginia, call 1-800-NEXT-STEP or text NEXT-STEP-253342 in Arizona. Visit 1-88- Call 1-88-789-777 or visit ccpg.org in Connecticut. If you're in Indiana, call 1-800-9 with it. Call 1-800-522-4700 or visit chaosgamblinghelp.com in Kansas. If you're in Louisiana, call 1-877-770-STOP. If you're in Maryland, visit mdgamblinghelp.org. If you're in West Virginia, call 1-800-Gambler.net in Wyoming, call 1-800-522-4700. Hope is here. Visit gamblinghelplinema.org or call<PHONE_NUMBER> for 247 Support in Massachusetts or call 1-877-8 Hope and Why or text Hope and Why in New York. NFL Sunday ticket offer ends September 18, 2023. No refunds, terms, and embargoes apply. 100 off NFL Sunday ticket, not YouTube TV. YouTube TV, base plan required to watch YouTube TV. Redemption requires Google Hant and current form of payment. Commercial use excluded. All right, let's hop into tonight's 11-game MLB slate to close out the week. We have a few weather notes to get to. They're not super concerning, largely, or all on the East Coast. The Yankees at home, the Phillies at home, Washington at home. All of these teams, a little bit of rain potential. Weather comes right at the start of the game, right slightly after the game begins, whatever might be. Minor rain concerns for all three of those. I'm not worried about that, Mo. Still be looking to hitting and really hitting in most of those spots. Don't really like any pictures from those matchups. Boston is at home. Maybe some, you know, rain later in the game as those cities will see the rain earlier, but it is nice and warm there and we do have some wind blowing out to left. Fenway is already an awesome hitters' park, so a little bit of wind is always a boost for the hitters. Let's get to the pitching on tonight's slate, which is pretty interesting. Up at the top, I will say there are a number of pictures I think are a little bit too expensive for my liking, but let's hop in. We have Kota Senga at 10.8. Blake Snell at 10.6. Kyle Bradish at 10.5. Jordan Montgomery at 10,000. Mitch Keller at 9,700. Eru Perez at 94. Griffin Canning at 9,300. Brown at 9,100. And Yusuke Kukuche at 9,000. Dollars options that round out the players that are above 9K. I think it's easy to say that Blake Snell is absolutely the best pitcher who's on tonight's slate. I don't think there's really too much of a debate for that, but he's on the road going up against Houston who are signaling putting up four or five home runs every single game and it's really not my favorite spot to go and rostering a pitcher against Houston is never something I'm super comfortable with because of this. And because we have Senga here up against Minnesota, I'm going to touch on him in the second end Montgomery for Texas going over against Oakland. It's pretty clear those pitchers should be a bit more popular than Snell. So if you want to go to Snell as a pivot, go for that, you know, toward an angle with Blake Snell, I think that is very, very clear. But Senga is in an awesome spot for the Mets. Obviously his first year in the MLB, he has a 29.3% strikeout rate, which is awesome. He has an 11% walk rate, which isn't great. He's only allowing 0.82 home runs per 9, you know, which is obviously very solid. He's mostly a medium contact ground ball pitcher coming with a 46.4% ground ball rate and a 52.7% medium contact rate along with a 3.96 Sierra, his skill interactive ERA. And that's, you know, all of this is great to see considering he's going up against Minnesota who right now at their current active roster, they have a 27.3% strikeout rate versus right-handed pitching, which is the highest in the league. This is the worst strikeout team against righties currently and Senga has an almost 30% strikeout rate. So when we look at this, we have to be saying Senga is in a spot to put up 8, 9, 10 strikeouts potentially. And the safety and relative upside that he brings compared to Blake Snell is pretty clear to me given the fact that Snell is going up against Houston. So that's why I'm going to be siding with Senga as like a 1A kind of situation over Blake Snell, who's, I don't want to say he's 1B, he's just more of a tournament angle. I would love him in tournament because I don't think he's going to be popular and obviously he's a side young candidate. He has plenty of skill in his own right. Jordan Montgomery is interesting tonight because of the matchup, right? And that's what it really comes down to. He's probably one of the pitchers that falls under the categories I mentioned.  He's 10,000. He's going up against Oakland. We know what we're going to be getting when it comes to Oakland. It's not an offense we're worried about in really any capacity. He has a 21.2% strikeout rate and that really just doesn't touch what Senga has up at 29%. Montgomery else comes in with a 6.5% walk rate, only 0.87 home runs per nine. And this is kind of in this thing. He's never been a dominant strikeout pitcher, but he generates a ton of ground balls. He generates a ton of medium contact. He does not allow home runs and it really allows, you know, him to kind of cruise to victories, cruise to easy victories and easy fantasy points because he could be racking up the QS, rack up the win points, whatever might be. And really, he shouldn't face too much resistance tonight, given the fact that he's going up against Oakland. Right now, Oakland comes in with a 22.9% strikeout rate with their current act of roster against lefties, which is 14th in the league. So it's about a league average matchup. But realistically, when it comes to Oakland's offense overall, it's not one that we're worried about. They have a 142 team Iso versus lefties, which is 24th in the league. They also come in with a 91 WRC plus in this same split, which is 26th in the league. So it's absolutely an easy matchup for Montgomery, who again, I would love to see five, six strikeouts out of him, six innings, you know, one or two run runs. And he just kind of cruises to an easy victory. But the reality is, is that his fantasy upside, I'm going to say, is not as high as Sangat and it's not as high as Blake Snow, who's just the best pitcher on tonight's slate and happens to be in the worst matchup. So up the top, I think it's pretty clear. You want the safety, you just roll with Sangat. You want to be a little bit different, I guess, is where you would go to Montgomery, but in all reality, the fantasy points in the upside probably lie with Sangat. And again, I really do like Blake Snow tonight, but it's strictly from a tournament angle. The question becomes, is where else do we go on tonight's slate? We don't, of course, field on tonight's slate. So there's no, like, must have stacked tonight. We do have the Braves, we do have the Dodgers who were in those kind of get-rate spots as I mentioned yesterday. Their offenses came through as we like to see. I think there are two pitchers that, you know, people will be looking at tonight and it's partially due to their salary and partially due to the matchup. One could be Yusei Kukuchi and 9000, obviously bringing a nice bit of salary relief, which is always good to see for the Blue Jays. He's at home, 25.2% strike away from him. He has a 7% walk rate this year, which is good to see it's really considerably lower than what he's posted over the past three years. He's up at 12.8%, 9.3%, and 10.3% walk rate over the past three years, and it's now down at 7%, which is obviously always good when we're looking to roster someone like Kukuchi. So the matchup versus the Royals, again not one that I'm too worried about. Yeah, they have some pop in their lineup and they're putting up runs here and there, but overall they're still coming with a 95 WRC plus with their current active roster versus lefties, which is 24th in the league. So given what Kukuchi is doing with some of his strikeouts, he's keeping the walk slower, this is a matchup where we could see some strikeouts from him because Kansas City come in with a 23.6% strike rate versus lefties with their current active roster. That's the ninth worst in the league. So given the salary at 9000 and the matchup, he makes an interesting case tonight because it's quite a bit less expensive compared to Snell or Senga up at the top. Now the real answer for a lot of people tonight, if we're looking to save salary, I think it's going to be Kyle Harrison of the San Francisco Giants, a player that was recently called up. He is 8600. He's at home tonight in San Francisco, which is a fantastic pitcherspark and he's going up against Colorado. Now Kyle Harrison has been called up for just three starts. He has 15.1 innings pitched under his belt at the Major League level. It's an extremely small sample size, but man, he is racking up the strikeouts with a 32.8% strikeout rate this season.  He is allowing 2.93 homeruns per nine, but again, it's a 15.1 innings sample size. So we have to take that with a bit of a great assault. He also has a 13.18% swinging strike rate, which is absolutely unbelievable. He has a 3.51 Sierra. He has a 54.1% fly ball rate, which is really, really high and it's only an 18.9% ground ball rate. That's just due to the sample size being only 15 innings. These numbers will stabilize. His medium contact rate is at 45.9%. That could certainly stay that way, but the 54% fly ball rate, that is going to stabilize and drop. Thus, the homeruns up at 2.93, that will also drop. Now, his salary at 8,600 is very, very enticing tonight, given the fact that he's going up against Colorado, who right now with their current act of roster, versus left-handed pitching, coming with a 30% strikeout rate, which is dead last in the league. So Senga, for the Mets, versus Colorado, he's a righty. Minnesota strikes out at the highest rate versus righties and Colorado strikes out at the highest rate versus lefties. So we have two pitchers that are really, really good with strikeouts, Senga and Harrison, obviously, small sample size for Harrison. But these are great matchups for both of them. And Senga is up at 10.8, but Kyle Harrison at 8.6, this is some really nice salary relief for a pitcher that has looked pretty good in his first three starts. I don't want to get too ahead of myself, but he's a player that we could be using in DFS slimes for many years to come, especially if he has this type of strikeout ability, not to mention the fact that this is an awesome pitchers park. So at 8,600, I think this is what opens up a lot of salary relief and allows us to stack teams like the Dodgers and the Braves, who happen to both be in awesome spots tonight. So pitching tonight is interesting where there's kind of options at, I would say, different tiers, where we have Senga and Snell over the top, you want to be a little bit different, you could go to Montgomery, you can go into the summer in the mid-tier at Kokuchi, and you want to drop below 9,000, there's Harrison at 8,600. So all of that is good when it comes to pitching. Let's move on to stacks for tonight. Again, we have the Dodgers, we have the Braves on tonight's slate, I don't want to specifically touch on them, the Dodgers, they're going up against Mackenzie Gore, I think that's a fine matchup to attack. They had their get-right spot last night, the Braves, they're at home, they're going up against Mitch Keller. Mitch Keller obviously got off to a super hot start this season, he's kind of evened out and things have stabilized since then. Another great spot for the Braves, they're putting up home runs as usual. But there are three teams outside of those two that I particularly like tonight. One would be the Toronto Blue Jays there at home, they're going up against Kansas City Royals, I spoke about Kokuchi. Now for the Royals, they are expected to have an opener start this game. That would be Kyle Snyder, he's only going to pitch 1, 1.2, maybe 2 innings, not really going to be too much of that, but Alec Marsh should be following behind him. Marsh has 52 innings pitched at the Major League level, and this is his rookie year. He has a 24.6% strikeout rate, which isn't too bad, but he has an 11.9% walk rate, he's allowing 2.60 home runs per 9 with a 4.62 Sierra, mostly a fly ball pitcher at 46.6%. So when it comes to the Blue Jays, this is the lineup that I'm going to be really interested in tonight. They have some good power, they're relatively affordable. I'm not going to say that they're super expensive. Getting up to Davis Snyder, who's now the most expensive hitter on the Blue Jays, which is a surprise to I think a lot of people, at 3900, Vladdy is 3500. George Springer is 3400. After that, it drops below 3K with Maryfield and Varshow. Brandon Belt, whether he plays or not, he's at 2900. He's listed as day-to-day. But the power from some of these players is pretty clear, especially when we're looking at something like Davis Snyder comes in with a 371 ISO versus Wright. Now, granted, he only has 44 plate appearances recently called up, so we do have to take that with great assault. If Brandon Belt is good to go, he's certainly a player. I'll have interesting getting into my lineup is not only because of a salary, but a 241 ISO in this split is something that we are excited to have in our lineups for that power upside. Vladdy, of course, is super solid. You can look to George Springer, Matt Chapman is still on the IL, so they're going to be, you know, continuing to mix and match their lineup. If you want to throw in Alejandro Kirk, that is certainly a viable option as well. Dark Dalton Varshow, all of these players are going to be in the mix tonight.  So the homerun upside going up against Alec Marsh, I think he's pretty clear with that fly ball rate. Not to mention, he also allows hitters on for free with an 11.9% walk rate, so it's kind of the mix that we love to see. He's not striking out hitters at a too high rate. He lets them on for free and he allows a ton of fly balls, which do present a ton of fantasy upside for the opposing teams. Next, let's take a look at the Baltimore Orioles. As I mentioned for Fenway Park tonight, it's warm. There are a little bit of wind blowing out to left, which is obviously good. That's a, it's already a good hitters park. And we have those fantastic hitting conditions or weather conditions on top of it being a great park. Tanner Hauke is going to be on the mound for the Boston Red Sox. A picture that's kind of really just in the middle in a lot of things. He doesn't strike out hitters at a high rate at all. It's at 21.3%. He has 1.21 homeruns per 9, 8.2% walk rate. He has a 4.28 Sierra. He's not really a fly ball pitcher. His fly ball rate is actually 27.4%. It's actually pretty low. But he's a pitcher that just kind of gets hit around in terms of single double walk, single double walk, whatever it might be. And all of a sudden there's three runs on the board before you know it. There may not be that massive, massive homerun upside because that's just not his pitching profile. But again, there's a little bit of wind blowing outside, which is always good to see. So he's a pitcher that is again going to get hit around. And the Orioles lineup is just kind of built for that, where they don't strike out a whole lot and they legitimately have six hitters right from the jump that I'm going to be willing to have in any lineup, really throughout the majority of the season when we go into Baltimore. Anthony Santander, Gunnar Henderson, Cedric Mullins, Ryan Mountcastle, Adley Rochman, and Austin Hayes, ranging from 3,700 up at Santander down to 2,900 at Austin Hayes. All of these players are putting up numbers left and right this season. And when we look to this lineup, Henderson, Santander, and Mullins all have ISOs over 200. Austin Hayes isn't that far behind. He's at 165. Adley Rochman is at 142. Although that's a lower ISO for Rochman, he has a super low 16% strikeout rate and he has 11.7% walk rate. So he is not wasting chances at the plate. He's putting the ball in play. He has a 324 Woba. And if he's not putting the ball in play, he's probably drawing a walk, which is only good for the stack when there's some of these power hitters around him. So, yes, Henderson, Santander, and Mullins are absolutely the top three when I'm getting with their ISOs that high, but I'm going to be totally fine taking two of them and going to Hayes and going to Rochman. Maybe taking some solid relief and going to Jordan Westberg, whatever might be just to get these hitters in my lineup. So Tanner Hauke is not a pitcher that I'm particularly worried about. Yes, I would love to see him have a 45% fly ball rate, but that's not the pitcher that he is. And we just got to take it for what it is, but he's a pitcher that I'm not worried about because he's going to be letting runners on base for free with a walk rate and then getting hit around, I should say, for some singles and doubles, which will present a lot of scoring changes for the Orioles. So that's the route I want to be going. It's already a great hitting park. There's a little bit of extra weather in our favor and we have six different options from the Orioles that we can be going to tonight. Finally, I want to take a look at the Milwaukee Rourers. They are on the road there visiting the New York Yankees. Luis Severino is on the mound for the Yankees, a pitcher that just simply does not have it this season. I know a few of his recent starts have been good, but they've been good relative to the lack of production that he's put up to this point in the season. He obviously started the year late, but man, he has an 18.5% strike rate this season. 8.3% walk rate and he's allowing 2.32 home runs per night. And this is from an 85.1 ending sample size. So it's pretty decent at this point where he just does not have it on the mound in terms of making hitters with. He's allowing way too many home runs. His a 37.8% fly ball rate. And what I like mostly about Milwaukee tonight are their salaries where they are very, very affordable. Christian Yelich is their most expensive hitter at $3,400, which really isn't that bad. Contreras is $32, Adonis is $31, and Santana is $3,000. So realistically, they're not a super, super expensive team to be stacky.  He's been looking good since he's with the Brewers since the trade, since the trade specifically for Mark Hanna. I think between his salary and his spot in the lineup is what I'm going to be most interested in. Obviously, I want to be getting up to Adonis, Yelich, and Santana for their higher ISOs that are all sitting at $176 or above. But Mark Hanna is not someone you should be sleeping on tonight in terms of his salary. He doesn't strike out. He puts the ball in play, et cetera, et cetera. Same thing with like Adley Rochman. Like, yeah, Hanna can go for some home runs here or there, but it's really just the power of the stack around him that makes him an interesting option. So when we're looking to stack the Brewers or the Dodgers or whatever team it might be, we want to pay it for pitching for players that are above $10,000. We need the salary relief. And when we have a team like the Brewers that are in a plus match against Severino that have a great hitting environment in front of them with Yankee Stadium, I want to be taking three of these options that are $3,100 and below. Adonis, Carlos Santana, and Mark Hanna at $31,000, $3,700. I think we'd make a great three-man stack to pair with the Braves, to pair with the Orioles, and still try and pay up for one of those top pitchers. So that's the route I'm looking tonight. We got some good power out of a value stack last night with the Tigers. Hopefully, we run it back tonight with the Milwaukee Brewers. So that's really where I want to be going. Let's kind of close things out. There's plenty of good teams on tonight's slate. If you want to be going to Texas, going up against Oakland, I fully understand that. If you want to be going to the Angels, going up against for Cleveland, Cleveland has, what is it, Logan Allen on the mound? A picture I'm not particularly worried about. If Otani's in the lineup, maybe I'll have interest in him getting to Gritchick. Maybe some one-offs for some power, but really not much outside of that. When it comes to Dinger calls on tonight's slate, you know, we're looking at some pretty easy matchups for a lot of teams. I guess I could go with Carlos Santana as one of them, just his power as a lefty swinger at Yankee Stadium, going up against Severino. It's something I'm going to be particularly interested in tonight. I don't think that's too much of a surprise. And then the team I didn't touch on specifically would be the Texas Rangers and Corey Seager going up against Paul Blackburn. I like Texas tonight. Adoles Garcia is on the IL now, so it certainly makes their lineup a little bit weaker, and they've kind of been struggling overall. But Corey Seager is still putting up numbers left and right. So I'm not thrilled to be going to a Texas stack just because, again, their inconsistency is there, but Corey Seager is still mashed in the ball. And I will take Seager and Santana as homerun options tonight. All right, so that does it for today's podcast. I will be back next week. I will be back to close out the season for the MLB while Jim is handling a ton when it comes to NFL. As always, this is one of the many shows on the Fandall Podcast. Network, you can find that anywhere, whether it's on Apple Podcasts, whether it's on Spotify, the video version can be found on the Fandall YouTube page. It can be found on Fandall TV Plus. It can also be found on Fandall.com. Watch. You can follow me on Twitter at TomLunderscoreVecchio1. And until next time, good luck in your contests.


The Titans relationship with Second Harvest Food Bank. Next week is Thanksgiving and Amy Wells, the team works hard with Second Harvest to help people who don't have as much as a lot of us do. Absolutely, in a season of eating, you know, and giving, it's good to have this partnership with the Tennessee Titans and Second Harvest Food Bank. We took some time to go over there and talk to them about keeping the spirit of giving alive all season long. It's a really big deal for us because the voice and the strength of having the Titans and the Titans players in the community and the fans seeing that hunger is an issue and that they really can't help is a big deal. For Nancy Keel, being part of Second Harvest of Middle Tennessee does not feel like an extraordinary act. For her, it feels like the least she can do.  And don't we all deserve that? People should have access to food and they should be able to afford the food they need. This means more than just hosting a canned food drive around the holidays. This is a year-round effort featuring numerous outreach methods all with one purpose, getting food into the hands of those who need it. If you think about Middle Tennessee, there's just about 360,000 individuals that are food insecure. And so our whole goal is to not only get the food to them but also to help touch their lives and improve their lives. For Second Harvest, getting the word out is paramount to generating community support. When the NFL Draft came to town in April, it created a huge opportunity for the Food Bank to quickly gather contributions, including one from the Tennessee Titans. What was great for us is, first of all, it brought together the entire community who didn't want to be involved with that. And then when we were there, the Titans gave us a gift of $50,000 that we didn't know that we were getting. And we were so blown away and so excited about it. And again, going back to that, $1 will provide four meals. That was 200,000 meals that came out of that one-day event. And then it also provided every single person that was there helping sort. They became aware of the issue. Support from the Titans not only raises awareness, but it also motivates a hardworking group of people who don't always see the fruits of their labor. What it does for the other volunteers and our staff here, it just blows their mind because it just shows that no matter who we are, what we do, giving back can impact all those around you. And that says a lot about the Titans that they'll allow to have their players come here and that the players will get involved.