Good morning. Welcome to this session. I am Mohamed Atef, and I am representing MCI. And as you can see, this particular presentation is a joint presentation by National Computational Infrastructure in Australia and Melanox Technologies. So the title is Chasing the Rainbow in Pursuit of High Performance OpenStack Cloud. So before I head to the main presentation, I'll just give you a bit of overview of NCI. What is NCI? NCI is National Computational Infrastructure, and it is Australia's most highly integrated e-infrastructure environment. So we have got a petaflop system, which was the first in Southern Hemisphere. We have got around 25 petabytes of luster storage, which is, again, we have got the largest deployment of luster in Southern Hemisphere, as well as we have got a high performance cloud. So in short, this is what we provide. We are located in Canberra, Australia. And for those of you who don't know, Canberra is capital city of Australia. Most of the people confuse Sydney as a capital of Australia. So NCI provides a full broad spectrum of research. So we have got users from pure sciences, strategic sciences, applied, and industry. You name a field, and there would be a researcher probably doing some sort of batch processing or cloud computing or big data analysis at NCI. Today, NCI is around 2,500 active users who actually log on to our system. So this particular 2,500 is people who have actually submitted jobs in past four months. We have got around 500 projects. We have got eight out of 22 science academy fellows. And our name is in around 1,500 academic papers per year. NCI is divided into two basic components, services and technologies. I am part of the services and technologies. We look after the infrastructure. And then there is another group, which is research, engagement, and innovation. These are the people who actually are trying to optimize HPC applications or working on virtual environments or data collections. So coming to the cloud, this is what we are here for. NCI has been doing cloud computing since 2009. It's a long way back. So initially, we started with a VMware cloud in 2009. We were doing web services at that particular point in time, mission critical, dual-site redundant, live migration via VMware. OpenStack was, I think, not even born then. So that's why we were using VMware. Then in 2010, this was our first HPC in virtualization. We came up with DCC cluster, which stands for Data Compute Cluster. And cluster again, so it's redundant. But we ran this particular cluster, which was partially virtualized under VMware. So it had few components, which were bare metal. And then there were few virtual machines, which were part of the cluster. And it was using 10 gig ethernet, Intel, Xeon, Vesmeer, CPUs. And it was basically used for workloads that were not typically suited for an HPC environment. So we run a supercomputer. And there was a workload which required installing Oracle Database inside a compute node. Technically, if you ask any HPC facility, can you do that? They are just going to refuse, flatly. What we did was, because we had virtualized environment, we were more agile. So we installed Oracle Database inside a compute node and let people do their processing. This was also first time, I believe, in Australia, that we actually oversubscribed HPC facility. So DCC, virtualized cluster, we were using oversubscription of CPUs. The reason being, there were workloads which were not exactly HPC workloads. They were actually high throughput. People were not looking for, my application should finish in 20 minutes. They said, I'm fine if my application finishes in 30 minutes, and if I'm able to run 10 more applications, because they were embarrassingly parallel applications. So we actually experimented with oversubscription of CPUs and it worked brilliantly. Then this particular cluster was, again, one of the first clusters in the world which actually had native luster mounts for the virtual machines. And it was based on Onsis diskless boot for VMs as well. So we were not actually using disks. So we were using Onsis, so it was diskless booting of virtual machines. Then in 2010, again, we had an unnamed cluster. I don't know why we didn't name it. Probably we didn't care. We just called it cloud. So for this one, we actually experimented with EC2. It was first experimental EC2 cloud. We first experimented with eucalyptus. You might have heard of that particular infrastructure. It's just like OpenStack, EC2 compatible. And we just couldn't get eucalyptus to become stable enough. And in two months' time, we saw the light. We moved to OpenStack. And believe me, in two weeks' time, we were production with OpenStack. So our experience with OpenStack in 2010 was quite good, which is against most of the people. You would hear from people that it was not stable, but it was quite stable. Then in 2012, we had another Red Hat-based cloud. And surprisingly, in Monday's keynote, I found NCI's logo when the CTO of Red Hat was presenting. So yes, we partnered with Red Hat. It was an enterprise-grade cloud, predominantly for virtual machines, nothing to do with HPC. The best outcome for this particular OpenStack cloud is that its uptime is 100%. It never really went down. 2013, we partnered with Nectar, which is basically Australian consortium for virtualization. And we made this Nectar research cloud production. So NCI basically is one of the eight nodes in Australia, which is part of this Nectar Federation. The main essence of this federation is that Australian researchers should be able to launch their virtual machines, and they should give them frictionless environment for conducting their research. Our node is consisting of Intel Sandy Bridge 3200 cores with hyperthreading. And we were the first, one of the first clouds in the world, which actually used full-fat, factory 56 gigabit ethernet provided by Malinox. Yes, when we were going production, we were questioned by a number of people. Why are you going with such an expensive network stack and such expensive CPUs? Most of the people at that time were thinking, we should go with 10 gig ethernet plus AMDs. But once we've given production, people saw why we opted for expensive Intel processors and full-fat, 56 gig ethernet by Malinox. So each of these compute nodes, so this whole cloud was based on the experience from our DCC cluster. So in this particular case, we went with SSDs on the compute nodes in rate zero format. So the local storage is very fast. We have access to half a petabyte of self storage, which is, again, part of the same fabric. It's not coming from 10 gig links. It's part of the 56 gigabit full-fat tree. And there is one issue with this particular cloud, and that is we cannot provide luster to this particular cloud due to security models. I will talk about this thing later on. In 2013, we launched our flagship cloud. We called it Tengen. It's a god of scholar in Japanese. We are going with Japanese themes nowadays at NCI. It's the same hardware as that of Nectar, full-fat tree. But we have divided it into two parts. One part is high-density zone, where we are using over-subscription of CPUs. This is for web services or burst reloads. And then there is another zone in this particular cloud, which is high-performance computing zone. It has got one-on-one ratio, so no over-subscription of CPU, memory, or any other thing. Based on RDO with Neutron, and we are on CentOS 7.x, whatever is the latest CentOS, we just update that thing. Architecture for big data. The main differentiating factor of this cloud with Nectar is that this one has got access to luster, because we can control who gets access to luster on this one. Plus, we also have access to SRIOV, single root IO virtualization by Mellanox. I'll talk about this thing later on as well. We are experimenting with bare metal or InfiniBand cloud, so no ethernet involved. It's based on Icehouse. It's fairly old, heavily modified by NCI, and Mellanox, so we are working quite closely with Mellanox on this one. And if we are able to get native IB working, we'll just move tension to InfiniBand. We call it InfiniCloud. And then we are also conducting some experiments with containers. We have used Docker on our cloud, and we are soon going to experiment singularity, which is another concept. It's just a container, but I believe much more suited for HPC. Systems connectivity, this is a very, very important slide. You would get to know why NCI is building OpenStack Cloud, despite the fact that we have got one of the biggest clusters in the world. So we have got Rygen, and then its file system, which is red, Rygen file system. Around 7.6 petabyte of slash short storage, it is 150 gigabytes per second, fastest file system in Southern Hemisphere. But we cannot export. In fact, we do not export this file system anywhere else. It's sandboxed. It's for the supercomputer. Then NCI also has got slash g slash data. So we call them global data. And as you can see, these are again luster-based, around 25 petabytes of usable storage connected via 56 gigabit InfiniBand. And these three file systems, or four or five, whatever we continue to grow these things, they are mounted across our supercomputer, as well as our OpenStack Cloud. And it's also backed up to our mass data tape storage. Why? We want to give people end-to-end solutions. So their workflow, if you are working on a certain project which requires pre-processing of your compute jobs on cloud, you can do so on cloud. Then you can submit your job onto a supercomputer. You get the results. You hop back onto cloud. Do some processing, post-processing. Visualize it so everything at NCI. So you don't have to shunt your data here and there. So this is what I was talking about end-to-end data lifecycle. One of the examples, you get your data into NCI, one-time operation, or you can even generate data at NCI. You do your data management, pre-processing of jobs, submit the job to HPC, get the results, visualize it, use MATLABs of the world using our cloud or virtual desktop interface. A few of other examples that we have, why we use OpenStack at NCI is we are part of Earth System Grids Federation, which is IPCC project. So I guess it won the Nobel Peace Prize in 2003, IPCC3 version. Again, what people have done is they have generated their data on our supercomputer. And now they are exporting this data to researchers around the world using our cloud. And it also enables researchers to do web-time analytics of the data. It's predominantly for climate sciences. Another interesting thing is we have got environmental data virtual labs. We call it climate and weather science laboratory. It's a virtual desktop environment, again, because G-data is mounted across supercomputer and cloud. You can pre-process your jobs, do a remote job submission. You don't even have to log into our supercomputer for this thing. Again, virtual desktops are being used at NCI. It's one of the most utilized features. And people are using it for a number of their tools. We have got a lot of virtual laboratories, which are production, geophysical, geodesy, climate, water laboratory, and more and more are being added at NCI. One of the first uses of cloud at NCI was for this particular project, which is water indentation due to a tsunami. So basically, if there is a tsunami, let's say, or an earthquake around New Zealand, we can simulate it using OpenStack Cloud and get to know about water indentation in Sydney area or any other coastal areas. So this is the architecture of Tengen. Everything is based around IB switching fabric. So I'm not going to go into the details, but yes, we can mount cluster. We have got Ceph. We have got other things. But everything is centered around our IB switching fabric, which is using a melanox 56 gigawit ethernet. Now, virtual labs and other stuff, they can exist on AMDs of the world in Tengen ethernet. Why NCI is using high-performance cloud? So this is statistics from our supercomputer. It's a bit year or year and a half old, but this holds true for every quarter. So this one is for only 43 days, where we actually catered for around 621,000 jobs in 43 days. It's a lot of jobs on a supercomputer. What you can see here in the upper right is number of cores. And this red line is 16 cores or less. Jobs requesting 16 cores or less. In terms of CPU hours or real workload, it's nothing. We are dominated by 256 CPU jobs, 512 CPU jobs, or 4096 CPU jobs. So most of the people have gone parallel in HPC. They don't really want to run, I shouldn't say, puny jobs, which are on a single node only. So this doesn't do justice to a supercomputer. But having said that, if you look at number of jobs, not the CPU hours by these jobs, number of jobs, single CPU jobs are over 300,000. So out of 620,000 jobs, 300,000 jobs, half of these jobs are single CPU jobs. These jobs are essentially for pre-processing or post-processing. Ryjin, or a supercomputer, is basically a batch operating system. If you are using it for post-processing, you might have to wait for one or two hours or three hours for your job to actually get scheduled. And then interactive analysis, they are possible on a supercomputer, but it's still painful. So this is one of the reasons we have gone with high-performance cloud. So for us, high-performance cloud is to complement the NCI supercomputer. Single-noded jobs are not big fun for a supercomputer. So we invest a lot of money in a supercomputer. We want to utilize the network the way it should be utilized. We want virtual laboratories. We want remote job submission, web services, on-demand access to GPUs. We have done this thing. Workloads, which are not best suited for Luster. So probably all of you know about Luster. It's a parallel file system. But one problem with Luster is it doesn't really play well with jobs or applications which are writing tiny IO. So IOPS-hungry applications do not scale at Luster. And this is where we are using CIF or other file systems experimenting with other file systems. Then there are pipelines which are not best suited for the supercomputer. Like the example Oracle database requirement inside a compute node, never going to happen on a supercomputer. But on cloud, why not? We want to do cloud bursting, more on this one later. But the idea being once our supercomputer runs out of capacity, we should be able to seamlessly migrate single CPU jobs onto a cloud. We are, in fact, experimenting this thing with Amazon as well. So that if somebody has submitted a job at NCI, a lot of jobs are there. We are out of capacity. We should seamlessly migrate their jobs onto Amazon. They get their job processed. And the results are then seamlessly transferred onto NCI data store. Student courses, RDMA is essential. You cannot do it on 10-gig ethernet. I mean, now you can do it because most of these providers are giving you RDMA. And the last thing is everything should be centered at NCI. You don't need to shunt your data back and forth. Everything should be at NCI. So a few of the experimental results. I'm going to quickly go through these things. So what I've done is we have compared Ryjin, which is our supercomputer, with Tenjin, which is our cloud based on 56-gig of a ethernet, with Tenjin again, but this time with containers. No virtual machines. We just went with containers. Plus, we experimented it with 10-gig cloud. I'm not going to name this cloud, but probably you all can guess. Point-to-point latency. I'm using OSU. I have state and university benchmarks for this one. It's point-to-point latency. That means there are two virtual machines. 16 CPUs each. But we are only using one CPU or one process per virtual machine. And we are sending data across, trying to determine what is the latency. Lower is better. The last line, the green one, is Ryjin, which is we want to beat this line. And the highest latency came out of, I forgot to remove this thing, AWS. The difference is so huge that I had to use log scale to show these results. But the main essence or takeaway is Tenjin Rocky is quite close to Ryjin, or native InfiniBand, which is a very, very good thing for us. So we further experimented with this thing. This is bandwidth results. Again, 10-gig ethernet nowhere near. But if you see this blue line in the middle, Tenjin Rocky, it climbs up after 32K and matches bandwidth that of normal InfiniBand. Why after 32K? Because we are using Jumbo frames on our cloud, whereas on Ryjin's side of things, MTU is set at 1500, so it's latency driven, whereas on the cloud, because it's for data processing. So we have opted for the MTU size. Then we ran some experiments using a single node job. This is for bioinformatics, which is the next big thing for HPC or in science. What you can see is Tenjin and Ryjin, they are just competing quite close to each other. When there is no network involved, in fact, we are beating Ryjin in butterfly benchmark because of SSDs, whereas Ryjin has got normal hard drives here. So this was quite an interesting result. Then we moved ahead with NAS parallel benchmarks. These are small kernels, which have got different communication patterns. For example, CG is neighborhood communication, and FT is Fourier transforms, which actually use all-to-all communication. In this one, the main takeaway, so what I'm doing is we are comparing 32 processes and 64 processes. And the results are normalized with respect to 32 processes on 10 GB cloud, which is gray. Now, what you can see is 10 GB cloud. It does scale, if you see, from the first gray and second gray, not that much, whereas we have increased the processes from 32 to 64. It's double the size of processes. It should have scaled well. It's not scaling. But if we look at Tenjin, it's not close to Ryjin, in any case, but it's scaling very, very well. So it's order of, let's say, four times faster than a 10 GB cloud, which technically makes sense, 10 GB and 56 GB. Another interesting thing is when we used containers, we caught results which were matching Ryjin. So if you are using containers with Rocky, you are going to get almost native performance. So this was a very, very interesting result for us. I'm going to skip through this thing. These are communication profiles. We then ran molecular dynamics code, NAMD. Everybody loves to run this NAMD code because it scales well. It's a real application. I have decided not to compare it with TenGig cloud because it was just using AMD's. Even with Intel, it was just very slow. So no point in showing that those clouds are slow. The main essence is Ryjin scales quite well. We have scaled it up to 128 processes, whereas Tenjin, which is using Rocky, in fact, it's not using Rocky. I'll tell you about this thing, but it scales quite well up to 64. It continues to scale, but this linearity goes away. So from 64 to 128 processes, it's not scaling that well, but it's scaling. Rocky, on the other hand, with containers, it is scaling well. I couldn't do experiments for 128 codes because I ran out of my test kit. We'll continue with these experiments, but one interesting thing that we found was the best results for Tenjin or our cloud using Melanox Interconnect was not with Rocky, not with Melanox MXM or Yala interfaces. It was with TCP interfaces. So the main takeaway from this particular thing, and we are going to experiment these things in detail, as well, is when you are running something on cloud, you have to be very, very sure what sort of underlying network communication or what we say in OpenMPI byte transfer layer, BTL, you have to use. We got the best results with TCP-BTL, whereas in NAS parallel benchmarks and other, we got the best performance from Yala interface. For bandwidth tests, we actually got the best performance from Rocky. So you have to make sure which BTL you want to use. One interesting thing is Numa. What we have found is this is an in-house application run by one of our guys. He's the developer of this code, and he suggested, my code is not scaling. It's not because of any network interface. It's because of lack of Numa. Please fix it. So I think Numa is now being made available with Liberty Release. I have not tested it. We are on Kilo, but this is actually hurting us. NCI is committed to HPC. We actually want researchers to get along with their research. Ryjin or our supercomputer is heavily, heavily over-subscribed, not over-subscribed, but very, very busy. So there are people who just don't get time. So what we did is we have released some open-source tools which behave like Ryjin. So your job submission script on Ryjin, our supercomputer, is going to run on these clusters as well. If you spin off your cluster on Nectar Cloud, so we have made it open-source. We also worked with Intel and Amazon, and we have released Ryjin in a box using Spot Incidences. Spot Incidences is a fantastic concept where you just bid for your virtual machines. So rather than paying a dollar for your 16 CPU HPC virtual machine, you can just say, I'm only going to bid $0.29. And if the data center does not have that much of load, they make it available.  In those two minutes, you might be able to checkpoint your jobs. It's a fantastic concept. Have a look at our YouTube video as well, how to build a supercomputer using AWS Spot Incidences. If you are short in money, it's one of the best ways to get into HPC. Another interesting thing what we want to do is bring HPC clusters instead of bringing HPC to the cloud. Why not bring cloud to the HPC? It's controversial, but it's possible. So we can run containers and singularity inside our HPC cluster. We don't really have to spin it off using OpenStack Cloud. It's just an interesting thing. So my conclusion is, yes, HPC. We are still chasing the rainbow. I don't see my rainbow because there are certain aspects where we are still not able to match the performance of a supercomputer. Parallel jobs run well on the cloud, but is it actually HPC? No, it's not HPC. Because in HPC, people ask me this question often, where did my cycle go? I cannot tell where your cycle went, because the hypervisor just ate it. Another thing is it's good for high throughput computing. So if you want to have a lot of jobs and you don't care about how fast your job finishes, it's perfect. Another interesting takeaway is single noted performance. It's at par with bare metal. Not a big surprise it was there. We wanted to have hardware performance counters on virtual machines. I think KVM has made it available now, starting from Linux kernel 3.3. We have not tested it, but hardware performance counters are must if you want to go into HPC. People will just simply say, I'm not going to run this job on a virtualized cloud, because I just cannot find the characteristics of my job. Bare metal provisioning, all these other things are just technically I'm just ranting about this thing. But one thing that we found interesting was locality where scheduling is missing in OpenStack. Come on, guys. It's 2016 now. Locality where scheduling is a must requirement. It should be network aware. It should be new malware. We just cannot live with this puny or strange greedy algorithm that OpenStack uses by default. People are working on this thing. I saw a couple of very interesting presentations. So that's pretty much from my side. Thanks, Mohamed, for sharing your experience and the NCI benchmarks. So I'm going to start my part of the presentation, which is going to be short, by giving you a quiz. So I want to talk about basically some of my revelation about cloud. So this is a worldwide unit shipment of something, some electronics gadgets that you all know. Who can take a guess of what this would be? Come on. Almost. It's a digital steel camera. So basically, the shipment kind of peaked around 2008. And it started a steep decline around 2011 and 12. So who can tell me what happened in 2007? Yes. So basically, the first iPhone was shipped in 2007 that kind of coincided with the decline of the digital steel camera. So actually, we're seeing a transition. This is just one example. Basically, a transition from special purpose hardware gadgets and appliances and solutions to, in this case, it's a common mobile computing platform, which can be iPhone or Android, et cetera, et cetera. And now on the iPhone, you can actually run multiple software applications that realize the functionality of the special purpose hardware gadgets that you used to have. And they can actually do a much better job. For example, I can load up my Yelp, find a restaurant I like, call them, and find the directions, order, delivery, et cetera, et cetera, all within the same device. And over the years, since the first iPhone was released, the computing power actually increased about 84 times.  Maybe not all, but the majority of your workload. So this is a similar transition from a special purpose built environment to more of a common computing environment like the OpenStack Cloud. So if you went to the Monday keynote session, Gardner talked about bimodal IT.  So for the HPC cluster, it's really designed to provide high-performance computing and normally accommodates a single tenant, multi-users but single tenant. And it's really built for a large niche distributed workload. And sometimes they are tightly coupled. And you have to use RDMA to basically communicate between the computing nodes. And in terms of data isolation and protection, which is important for genomic research bioinformatics type of workload, it's really poor in the HPC cluster. And for cloud, it's really built for a different purpose. It's built for agility, for quick access to computing resources, ease of use, and experimentation of your ideas and elasticity of your resource pool. And it can accommodate multi-tenant and normally run more generic workload, loosely coupled. But it has really good data isolation and protection. So this is similar to, for example, a digital SLR camera that some of the avid photographers will definitely never get rid of. And an iPhone that has a good enough camera, but it's a common compute platform that can enable you to do many things very quickly. When we look at the workload, it's really not black and white. Web Services run in the cloud and HPC workload run in the HPC cluster. And we see the world more in 50 shades of gray. So the new generation of scientific research computing really has many type of workload that has different requirements on data isolation, on workload affinity, data access, et cetera, et cetera. And the key message of my part is, if you don't remember anything I say, remember this. So no matter where you draw the line, whether it's horizontal or depending on the workload size, Melanox always provides you the highest performance network for your data access and workload communications. So how do we do that? When we move to the cloud, it's not necessarily always true, but it's normally associated with virtualization so that you can run virtual machines and utilize your resources much better and have much better agility. But along with virtualization, there are a few kinds of penalties in terms of performance. With compute virtualization, it introduces a hypervisor. So with bare metal, you're driving down a very fast freeway. Now with a hypervisor, you're adding a Tobus. So you're slowed down, especially with IO performance. And with network virtualization and software defined networking, one of the very popular way of doing SDN is using overlay style. You're having an additional packet header, the VXLan or NVGRE header, to differentiate between different tenants. And not all NICCards and adapters can recognize this new packet format and handle it properly. And that actually brings some of the tedious packet processing tasks to the CPU, such as check some calculation, RSS and large packet offload, et cetera, et cetera. And also it's inefficient network protocols, transport layer protocols for thumb workload. If you look at TCP IP, it's really designed. It started from wide area network, from very lossy and slow links. So it has to accommodate packet loss at the link layer. So as a result, it has a lot of built-in mechanism to handle handshakes and sequence number checks, et cetera, that must be done in the CPU. But there are new generation of protocols that can eliminate this kind of inefficiencies. So how do we overcome these? We use SRIOV, single root IO virtualization, to basically overcome the compute virtualization penalty. So we enable you to bypass the hypervisor and the OVS and have application direct access from the virtual machine to the network NICCard itself. And then in terms of the SDN and network virtualization penalty, we have VxLan offload. Actually, it's not restricted to VxLan. It also supports MEGRE and in the future, Ginev. Basically, if you look at the benchmarks that we run with multiple SDN partners, the light green bar shows basically bare metal VLAN performance in terms of throughput and CPU load. And the moment you turn on VxLan, if you don't have VxLan offload, you go to the red bar. So basically, it's significantly lowered throughput at a much higher CPU utilization. And then the dark green bar shows when you turn on VxLan offload, you basically go back to bare metal performance. So this gets increasingly important when the speed of the interconnect goes up from 10 to 25 to 40 to 100. And to overcome the transport protocol inefficiencies, we use RDMA. So I don't need to explain RDMA in the HPC community. It does kernel bypass and protocol offload. And all the data IO operations can be done in the NICard itself without CPU involvement. And as a result, we run data IO in both InfiniBand and Ethernet networks at 100 G BPS. So for OpenStack, we want to enable you to run at your optimal extreme performance no matter what you choose. If you want to use the InfiniBand, we have OpenStack over InfiniBand. And the ML2 plugin is available since the Havana release. And we do the translation from your MAC addresses to mean that's offered in the OpenStack scenario to GUID. And we do the VLAN to PK partition K mapping. And InfiniBand is inherently software defined. The control plane and data plane are always separated. And in terms of Ethernet, not all Ethernet switches were born equal. So if you look at some of the dominant players in terms of Ethernet switching chips, such as Broadcom, they came from more of the campus and carrier Ethernet space where some kind of loss is acceptable, because the upper level protocols can handle it. And the Melanox Ethernet actually came from InfiniBand for the data center scenario, where we have very stringent requirement on performance and on packet loss. As a result, for our latest generation of Ethernet switching chip and Ethernet switches called Spectrum, supporting 10, 25, 40, 50, up to 100G, we have zero packet loss at any packet size, I mean down to the 64 bytes, smallest packet size. And we have low and consistent latency, as you can see on the bottom. Our latency is consistent from 64 bytes up to the jumbo frame 9K, as opposed to the Tomahawk chip, which gives you about 10 times of latency when it gets to the jumbo frame. And also, we have very good microburst absorption capability. So this is really important for data analytics type of workload, when you have in-cast. We can accommodate almost 10 times better microburst compared to the other switches based on Broadcom. So with that, I want to close. And if you have further questions, go visit us at boothstand next to the rock band. And I'll invite Mohamed to come up if you have any questions. Three, two, one. OK, thank you, everyone. OK, question. I had a question. In terms of building this purpose-built cloud, you basically tailored the cloud for performance. What were the trade-offs in that? That's my first question. And the second question is, what about the resiliency aspects? I think you show a number for 100% in the last two years. But I think that was for another cloud. It wasn't for Tegen. So if you can address those two aspects, thank you. So in terms of uptimes, Tegen has got an uptime of 99.8%. It went down for a while, but it was due to power failure. And we fixed it. The other question was, what did we have to sacrifice? Absolutely nothing, apart from spending a bit more money. That's it. Thank you. Thank you, everyone. Thank you for coming to our session.


First of all, I would like to thank your excellency, your chair, Nahayan, Mubarak Al Nahayan, for your message, your message of tolerance of uncoexistence, which is the title of your ministerial portfolio. And I think that all the ideas you expressed are exactly those that we share in this world policy confidence. So I want to thank you very much to thank the United Arab Emirates, who host us for this 14th edition of the WPC and all the friends with whom we have worked for this event. And you reminded us that not only is it the opening of the Expo in Dubai, but you reminded us that it is also the 50th birthday, Jubilee of the UAE. And let me also, in the name of everybody in this audience, wish you a happy century, not only 50 years, but a whole century to come. And we need very much this wisdom you have spoken about just to survive because it is a matter of survival. And now I would like to ask your holiness, Patriarch Bartholomew, to come, who is an old, if you allow me, old friend of the WPC. You have been so many times with us, your holiness. Prime Minister Eddie Rama from Albania, who has been also with us. I think this is the second time. Prime Minister Rama, Prime Minister Patrick Aschi from Ivory Coast, who, the Ivory Coast is also one of the countries with whom we have had regular participation. And thank you very much also, Prime Minister Aschi, for being with us tonight. And Mr. Walid Elke Heridji, who is the Deputy Prime Minister of Saudi Arabia, representing Prince Faisal Al-Farad Al-Saud, who could not come today, but the Deputy Prime Minister will deliver a message in his name. And after all this, I will start by my own presentation. And after that, when you have finished, you have the Ambassador, the French Ambassador, the Ambassador of France in Abu Dhabi, Mr. Xavier Châtel will also take the floor and deliver a message. So, Excellencies, I'm particularly happy that the 14th edition of the World Policy Conference is taking place in Abu Dhabi, nearly two years after the 12th edition in Marrakesh. The absence of the 13th edition in the WPC timeline, like buildings in the United States without a 13th floor elevator stop, or planes without a 13th row will always mark the year 2000, which will stand out in the history of the contemporary world. The shock of September 11, 2001, the 2007-2008 subprime crisis, by the way that was the first year of the WPC, and its aftermath, the very poorly named Arab Spring, early in the following decade, the COVID-19 pandemic, and of course climate change, whose effects are now being felt in the everyday lives of people around the world, are some of the early 21st century events that recall the fragility of the human condition in both its collective and individual dimensions. Geopolitically, the fall in the international system since the fall of the Soviet Union combined with the meteoric rise of China, whose ambitions are increasingly clear, remind those who dreamed of a blissful age of globalization that the flat world of its ideologues was an illusion. In some respects, ladies and gentlemen, in some respects, today's world resembles that of the early 20th century, when the lack of any sort of global governance to use a contemporary term led to the first world war. The pandemic, whose outcome is still very uncertain, has accelerated technological and social transformations already well underway, while the sudden hardening of the Sino-American rivalry has intensified changes in the world and the ensuing uncertainties. Many observers, even well-informed ones, have not seen or wanted to see that Joe Biden's election would not change the course of US foreign policy, which now focuses entirely on China. Biden's style is certainly more traditional than his predecessors, but his actions are no less abrupt and unilateral. Hopes for a return to multilateralism or at least consultation between allies in bodies like NATO have faded. The conditions in which American forces were withdrawn from Afghanistan and the announcement of a new alliance between Australia, Great Britain, and the United States are two recent examples. They are unlikely to be the last. If states like Japan and South Korea have reason to believe that they are safe from Washington's about-faces, it is because US interests are very important there. Many other countries feel the need to brace themselves for profound reconfigurations or even regional conflicts in which the United States would only be marginally interested, like nature, geopolitics, a boss, vacuum. This was recently seen in the Middle East under Trump's presidency when Russia and Turkey flexed their muscles. Confrontations on a more or less large scale are likely wherever the interests of the United States or China are not directly at stake. Where they are, as in Taiwan, head-on collisions are inevitable in the next few years, unless the new world's two superpowers establish a dialogue comparable to the one the United States and the Soviet Union set up after the 1962 Cuban missile crisis. Perhaps it would take a crisis of similar magnitude to get there. Another source of concern is the growing politicization of the economy and finance, notably through sanctions. Until now, this has mainly been an American weapon, but China can be expected to methodically resort to them. More broadly, each of the two rival superpowers intends to develop its own globalized system, which should result in two competing spheres in the cyberspace and new forms of dividing the world up into zones of influence. However, most countries do not want to find themselves having to pick sides and thereby becoming vassal states. This is especially true of the European Union in general and its component parts in particular. Of course, Europeans have a major interest in preserving freedom of navigation in the area now known as the Indo-Pacific, and they unreservedly contribute to this. They attach great importance to deepening their relations of all kinds with India, Japan, and South Korea. Naturally, the European Union's member states feel culturally and therefore politically much closer to the United States than to China. Europeans cannot show themselves to be equidistant, and they say it, and yet their interests with regard to Asia in general and China in particular do not exactly coincide with those of the United States. Far from it, they could not accept an imposed transformation pitched as preventive of the Atlantic Alliance into a de facto American organization aimed against China. Their main immediate security interests have more to do with their neighbors' instability. It would make good economic, political, and geo-strategic sense for Europeans to collectively structure their ties to their southern neighbors, the Middle East, Africa, and naturally Eastern Europe, including, and I stress this point, Russia. All of us should focus our efforts, mainly on relationships with our neighbors to boost the chances of harmonious economic and social co-development, and here I speak like the Chinese, while giving ourselves the most autonomous means possible to build the collective security of this vast region whose peoples are designed by history and geography to live together. This, of course, does not mean working against the United States, but nor do we want a confrontation with China beyond what preserving our essential interests requires, for example, in the area of technological sovereignty. That said, there is a precondition for keeping the global peace in the coming decades, an understanding between the United States and China based not on a sort of division of the world, but on the contrary, on what can be called humanity's common interests, starting with health and the climate, as we are now discovering or rediscovering. If this condition goes unmet, other states will be unable to successfully meet the tremendous challenges the world can be expected to face in these areas in the coming decades. With a bit of optimism, and as you would say, excellency of wisdom, strong cooperation between the two superpowers on humanity's common good could hopefully extend to other issues. These few thoughts are not meant to be pessimistic, but lucid. More than ever, I believe in the WPC's calling, as it has been defined since its inception in 2008, medium-sized powers must work together to put across their views on the conditions required to keep the world reasonably open. That is, globalization without hegemony or any form of extremism. It seems to me that this idea is shared by the United Arab Emirates, which is hosting us today at the very time, as I recall, as your excellency recalled when the Dubai World Expo is opening and your 50th birthday anniversary, whose symbol is precisely, I'm talking of the Expo, whose symbol is precisely balanced globalization through the smart, reasonable use of technological resources. The entire Middle East is suffering, but the region potentially has everything it takes to again become a place of hope and prosperity. Moreover, everyone has become aware of Africa's immense resources. Europe, if it manages to surmount the challenges inherent to its integration, could become even more of what it has been in the past decades that is a pool of prosperity, freedom and peace that has renounced all forms of imperialism. It is clear that in the world of shrinking distances, Europe in the broad sense, the Middle East and Africa form a community of destinies. I thank you.


Hey everybody, Lance Goyki here. Today we're discussing another pull-up variation, this one where I kind of scissor kick my leg. So one leg comes forward, one leg comes backward. What does it look like? So we're going to do our best. It's kind of like I'm walking, right? So one foot is ahead of the other and then my body is kind of turned because my hands are on a pole that is fixed. So my hands have to be straight here. So if I'm bringing one leg forward, one leg back, my body has to rotate that way. And then I'm just doing a pull-up with my legs in that scissor position. This is what it would look like if I switched. So it's easy to switch because your feet are just dangling in the air, right?  But that is the key. You need to turn your body for this. That's what makes it so unique. It's a lot like the side-to-side pull-up or the zigzag pull-up that we had talked about previously. What I'm doing is I'm changing the position of the core. I am teaching you how to twist and how to contort in different ways so that when you pull yourself up, you have different shoulder mechanics. You have different scapular mechanics. You have different ways that your body has to move to do the exercise correctly. So how do you figure out how to do this correctly? Well, the first, just do the position. But then second, you got to make sure that your shoulders stay evenly between your hands. That's kind of the way that I would try to fix this. If your grip feels even, you're generally adopting the right position. If I can feel my pinkies the same amount on my grip, then I am contorting my body in a way that lets me actually grip the bar while I am twisting. This is another good one. If you really do have asymmetries that you need to fix, if maybe one shoulder hurts but the other one doesn't or maybe one shoulder just likes to ride up while you do your pull-up and the other one doesn't, this is a good way to just kind of experiment around. So twist your leg and see which way feels better. See which way is harder and maybe practice a little bit more on the side that's harder and or maybe go slower on the way that's harder or maybe use less weight or more assistance on the side that's harder. And you can use this as an excuse to do all those things that you know are good for you but you're kind of avoiding because your ego won't let you. Too true, too true. A scissor kick pull-up. Great for introducing rotation, great for teaching the core how to turn on the right way and adopt the right positions and great for shoulder mobility while you're actually training your pull-up.


So hello, hello everyone and today we have some back in here today with us and the author of malignant self love narcissism revisited. Hello, Sam. Hello, thank you for having me again. Thank you so much because I know that you are busy and. Yeah, so. Thank you so much. Today I would love to speak with you about mortification and my first question will be what is mortification about because it's difficult topic and not so many people understand what is it and, you know, yes. Unfortunately, the leading the leading videos on narcissistic modifications which were made in the past few weeks are very misleading.  They confuse narcissistic modification with narcissistic injury, narcissistic wound and narcissistic scar. So I suggest to start by defining what what is injury wound and scar. And then we can go on to discuss narcissistic modification and then you will see the huge you will see the huge difference between injury narcissistic injury narcissistic modification. I'm again warning that the only credible sources for information about narcissistic modification in this particular case happen to be on my channel, because I have four videos based on the literature on the scholarly literature the academic literature. All other videos regrettably confused completely narcissistic injury and narcissistic modification. You should be very careful what you're watching and what you believe once you're watching. Let's start with definitions, narcissistic injury. And I'm reading is an occasional or circumstantial threat, real or imagined to the narcissist grandiose and fantastic self perception, the false self as perfect omnipotent omniscient and entitled to special treatment and recognition, regardless of actual accomplishments. So any threat to this self perception this inflated grandiose self view is narcissistic injury. narcissistic wound is a repeated or recurrent, identical or similar threat. In other words, narcissistic one is simply narcissistic injury that keeps repeating itself. So, if you have the same injury time and again, for example, from the same person, or in the same environment, or owing to the same circumstances, if the injury repeated self, it becomes a wound. And then there is narcissistic scar, narcissistic scar is a psychological defense against a narcissistic wound. The defense is intended to sustain and preserve the narcissist grandiose and fantastic self perception is false self. So these are the three things modification has nothing to do with narcissistic injury or narcissistic wound. Absolutely nothing. It's a totally different dynamic with totally different outcomes for totally different reasons. The etiopathology, the etiology, the coordination of modification is very different. The whole process is very different. And it's a great misfortune that people online are confusing. So now if you want, we can discuss narcissistic modification. Yes, please. Okay. We start with phenomenology. How does it look? How does modification look? So, modification happens only when there is someone, a human being, who aggresses against the narcissist, becomes aggressive with the narcissist, shouts at the narcissist, humiliates the narcissist, attacks the narcissist physically, verbally, psychologically, in any way. So, there must be an aggressor. Condition number one. Condition number two, it must be in public. Not, not privately. Modification never happens privately, only in public. And not only any public, but the public that matters to the narcissist, for example, his colleagues, or his peers, or people he admires role models, and so on. So that's the second condition, public. The third condition, it must be sudden, unexpected, unpredictable, abrupt. The narcissist is not preparing himself, but it's like a thunder, and he's shocked completely, and he's without defenses. That is a third condition. Now, if these three conditions are met, an aggressing person, person who aggresses against the narcissist, suddenly, in public, the narcissist reacts with narcissistic modification. So, what is that notification involves? Shame, humiliation, trauma, real trauma, not many trauma, severe trauma, depression, anxiety. And all these attack happen to the narcissist at the same moment. So, he's utterly overwhelmed and flooded. And this is, of course, a borderline condition. There's emotional dysregulation. What modification does to the narcissist? It strips away the defenses, the narcissistic defenses, like the false sale. And then what is left is actually a borderline, someone with borderline personality organization, borderline defenses. And the narcissist realizes the limitations and defects of his true self. In other words, the false self is disabled, deactivated. We call this process decompensation. There is no false self separating the narcissist from the world. So, reality impinges on the narcissist, touches the narcissist directly, without a firewall, without protection, without mediation. It's very direct.  In other words, the narcissist gets in touch or becomes aware of his internal bed object. This is how it looks. Now, the minute this happens, when the defenses are done, some really, really terrifying things begin to happen to the narcissist. I want you to understand that all this takes place within five minutes. Modification is not a process. It's not a process. Okay. So, how is this process unfolds when this, you know, when NPD sees himself or herself, right, without filter, without false self? At that moment, when the false self is disabled, the narcissist is no longer able to confuse external objects with internal objects. Remember, remember that in pathological narcissism, there is a confusion between external objects and internal objects. The narcissist internalizes external objects, and then he feels that he is in control. Because internal objects can be controlled. They never abandoned the narcissist. They never humiliate the narcissist. So, the narcissist prefers to be in touch with internal objects that represent external objects. So, if the narcissist is in touch with you, if he is in an intimate relationship with you, even if he's your friend or even if he's your colleague, he's going to create a snapshot of you, a photograph of you. And he is going to internalize it. He's going to interject it, and he's going to continue to interact with the photograph, not with you, never with you. This is a defense, because that way, the narcissist feels superior and safe. The object is inside his mind, so he is the boss. But, modification destroys this mechanism. So, the narcissist no longer is able to internalize you.  And so, the narcissist is in a state of terror, horror, disorientation. The force self is destroyed, and all the external objects invade the narcissist's mind, like Russia invaded Ukraine. All the external objects that the narcissist kept out, suddenly they intrude, they penetrate the narcissist's mind, and the narcissist is totally at a loss what to do. He feels hopeless. He feels like there's no alternatives. He feels helpless. And above all, he feels that he has lost control over his own world, over his internal world and the external world. So, he is no longer God. He is no longer perfect, because God controls everything. And so, the modification disables the force self. The external objects invaded the narcissist's mind. He became aware of the external objects. He lost control, and that means that he is not perfect. He is not Godlike. So, huge shame and huge humiliation that he is not God. Because the narcissist's defenses, I'm God, I know everything, I'm powerful. These are defenses against shame, against inferiority. And so, he doesn't have these defenses anymore. He literally disintegrates. He falls apart. He becomes paralyzed, disabled, depressed, anxious, and absolutely suicidal. Modification leads to two effects that are rare in narcissism. Number one, self-awareness. Self-awareness of the bad objects, limitations, defects, inabilities, inadequacies, deficiencies, deficits. This is new to the narcissist. This is shocking. And it comes as a river. It cannot stop it, you know, because the force self is disabled. And the second thing is, intrusion of external objects terrifies the narcissist so much and that when it is coupled with his shame over not being God anymore, he wants to die. This is a powerful suicidal ideation. Again, it's a borderline condition. Again, this is actually a borderline state. Modification is regression, regression of the narcissist back to borderline condition. Grozstein was a famous psychoanalyst. Grozstein said that narcissism is a borderline. I'm sorry, borderline is failed narcissism. Yes. The borderline wants to be a narcissist as a child, but she fails and she remains a borderline. The narcissistic child succeeds to become a narcissist, but the modification pushes the narcissist back in time to very early childhood when he was still borderline before he became narcissistic, because all the defenses are gone and he becomes borderline. He's suicidal. He wants to mutilate himself.  He's terrified of external objects. He has abandonment. It becomes exactly borderline. But the borderline is used to be borderline. She has experience. She developed defenses. She develops routines, procedures. She manages to survive with her disorder. The narcissist doesn't have experience how to be a borderline. So when the narcissist is suddenly overwhelmed and flooded with a borderline condition, narcissists develops major depression and extreme suicidal ideation. Very dangerous condition for the narcissist. He also becomes self-aware. So if there is therapeutic intervention, this is the time. Modification is the time for therapy, actually. Now, Liby, which is one of the great scholars of narcissistic modification, she described two types of narcissists, what she called the deflated narcissists. Today we call it covert narcissists. The deflated narcissists and the inflated narcissists. Today we call them covert and overt. So she said that when modification happens, there is an initial phase of paralysis. Narcissist is paralyzed. He's so shocked. All the experiences in modification are totally new to the narcissist. For example, direct contact with external objects. He doesn't know how to do this. Finally, being in touch with emotions. He doesn't know how to deal with emotions. The bad object takes over. His grandiosity is incapacitated. He doesn't know how to deal with all this. There's no fantasy defense. There's no cognitive distortions.  It's so shaming, humiliating, depressing, and above all terrorizing that he wants to die. That phase lasts anywhere from days to weeks. That's a very dangerous period if there's no therapy. Following this phase, the narcissist tries to rebuild his narcissistic defenses. And Libby describes a process which she calls internal to external modification. And this is a very interesting process. The narcissist, remember, is not grandiose now. The modification disabled the grandiose. Narcissist has been humiliated publicly, shamed publicly by an aggressive person. So he cannot be grandiose. So the narcissist tries to rebuild his grandiosity. How does he do that? By lying to himself, of course, that's what narcissists do. So he lies to himself. He says, this person who wronged me, this person who humiliated me, this person who shamed me, he did all this because I made him do it. I made her do, she cheated on me in public with someone because I pushed her to cheat on me. He stole, he humiliated me in public because I provoked him. The narcissist lies to himself that the aggression that he had experienced was because of him, of his behavior, or actually because of his misbehavior. He says to himself, yeah, people humiliated me, people shamed me, people attacked me, people aggressed against me, people were bad to me, evil even. But all of this because I made them behave this way. I controlled their behavior. So because I controlled their behavior, it means that I am God. I'm again God. They were my puppets. They were just my puppets. And I was the puppet master.  So he is lying to himself. This is called Autoplastic Defense. Autoplastic Defense says, I'm guilty. I'm responsible. I'm guilty. I made all this happen. I was in charge. I was in control. And even I'm evil. I did it because I'm evil. And then the narcissist restores his sense of control and sense of grandiosity because all these people who misbehaved, humiliated him, mocked him, laughed at him, attacked him, criticize him, disagree with him, all these people. They did all these things because he told them to do it. He was in charge. So this is called internal defense. Libby's term is internal modification. But then at some point, the narcissist, if the narcissist keeps saying, I'm the bad guy. I'm the bad guy. I'm evil. I pushed them to do it. I pushed this woman to cheat on me. I pushed this man to criticize me. I pushed the other men to beat me up. I pushed them to do it in public. I provoked them. I attacked them. I humiliated them. So this was retaliation, reactive abuse. But if the narcissist keeps telling himself this story, that means that he is a bad object. It means that he's evil. He's malevolent. And the narcissist cannot accept that he is a bad object. Because if the narcissist gets in touch with his bad object, he becomes suicidal borderline. That's very dangerous. So the internal solution for the modification, the solution that says I'm the bad guy and I made everyone behave badly. This solution cannot hold because it means your bad object is correct. So then the narcissist transitions to an external solution. So first stage, paralysis. Second stage, internal solution. I made them do it. Third stage, external solution. External solution is alloplastic. It's an alloplastic defense. External solution simply says these people are evil. They are malevolent and malicious. They are bad. They conspired against me. They are ungrateful, et cetera, et cetera. So now they are bad. Not the narcissist. The narcissist didn't do anything. They attacked him for no reason. So it's exactly the opposite of the internal solution. The narcissist's mind is very flexible. The narcissist can lie to himself that way. And then the next minute can lie to himself exactly the opposite. The narcissist can come of mental illness because the narcissist has no dissonance when he contradicts himself. Healthy people have dissonance when they contradict themselves. Not the narcissist. So now the narcissist says, forget my previous story. I did not provoke them. I didn't do anything bad to them. I was not the puppet masters. They were not my puppets. They are bad people. They're evil people. They did it on purpose. They were against me. And this is alloplastic defense. And then he develops paranoia. He becomes paranoid. He said, these people, they're my enemies. And they're going to persecute me. And they're going to pursue me. And so therefore I must destroy them. And the narcissist becomes psychopathic, vindictive and truly evil. Truly evil.  These people who cost him the modification because he believes. So yes. So what can we expect when we are mortified narcissists? When we are this aggressive person? He will come after you. He will transition. He will be paralyzed, depressed, suicidal. Then he will posture. He will say, you are nothing.  I made you do it. I was in control. You did what I wanted you to do. What you did, I wanted you to do. It was me and so on. And then suddenly, but very suddenly, because he cannot tolerate the bad object. He cannot say, I'm the bad person who made you misbehave. I'm the evil person. I caused you to cheat on me, to betray me. You know, he cannot say that because he cannot admit that he's a bad object. So suddenly he will move and you will become the bad object. And he will try to destroy you. He will become very vindictive. He will conspire against you. He will lie. He will try to destroy you in every way possible. He will become very vindictive in the long term. It can take years. It can take absolutely years. Until he's satisfied that he had punished you somehow. And that justice has been restored and balance has been restored. And his grandiosity and control have been restored. Because he's like God. God punishes the sinners. He needs to punish you because you committed a sin. You were sinful. He is God. You attacked God. This is blasphemy. You need to be burned on the stake like the Inquisition. So he has this morality. In his mind, he is a moral person for punishing you.  You are vicious. You are wicked.  And you must be punished. You must be taught a lesson. Or you must be removed from society, put in prison or something. You must be punished. Because if you are not the bad, the evil person. The narcissist is the evil person.  Either the narcissist deserves the modification. Because he's evil. He's bad. Or the narcissist is innocent. He's a victim. He didn't do anything wrong. And that makes you evil. Makes you wicked. And so you need to be punished.  That's dangerous. Very dangerous. Multified narcissists are vengeance machines.  And they are unstoppable. And never mind how many times they fail. They go on. They never stop. And because they lost their grandiosity, they need to restore it. And only you can restore it. The problem is you took away their grandiosity. Now you have it. They want it back.  Because you took away... If you disappeared from his or her life, what's then after modification? Not the same.  You were never an external object. You're an internal object. So you're always in the narcissist mind. Never mind where you go. You can go to the room. Yes, I understand this. But when you're disappeared, you moved somewhere or you changed job, whatever. Nothing. Because the narcissist has introject constancy. In other words, you are in the narcissist mind that really dies. And your introject is in the narcissist mind. The narcissist continues to interact with your introject, even if you divorced him 20 years ago. He continues to have dialogues with you. He continues to punish you or to correct you. And then suddenly he can appear after 20 years and continue like nothing happened. Because he did have a continuous relationship with you in his mind. You went away. You got married with children. I know what happened to you.  And so he doesn't see anything strange to continue the relationship with you after 20 years. Every day he had a relationship with you. Same with modification. You became a persecutory object. It's called a persecutory object. You became an enemy within. And he needs to eradicate this enemy. He needs to destroy this enemy. And where you are physically is totally irrelevant. Because the battle, the war is inside his head.  He needs to destroy you to match the external object with the internal object.  But the battle is ongoing in his head. And so he makes all kinds of conspiracies and plans. He stalks you. We attacks you. He goes to the police and lies. He would never stop. And of course, when I say he to be clear, it applies to women as well. That's just to be clear. Today, more or less, it's 50-50. Borderline and narcissism are 50-50. 50% male and 50% female. It's a dramatic change in the last 20 years. Because 20 years ago, about 75% of people diagnosed with narcissism were men. Today, it's only 50%. Women are becoming more and more and more narcissistic and by the way, less and less borderline. So this is a very dangerous situation because women are much more sensitive to modification than men. For example, it's much easier to modify a woman. All you have to do is criticize the way she looks. If you tell a man you're fat, you're fat, okay?  It will be narcissistic injury. If the man is a narcissist and you tell the man you're fat, it's injury, but it's never modification.  So women have many more options and venues for modification. Women are much more easily modified than men. They are much more sensitive on multiple levels, including the way they look, the way they eat, the way they dress. Men don't have all this. Men doesn't care if you tell them you're dressed badly. Okay, I dressed badly. What's next? What's on the menu? But you tell that to a woman and you do it in a shaming, humiliating way in public in front of her own girlfriends, for example, or women she competes with. And you definitely might create modification and then you're her enemy for life until she destroys it. So the rise in narcissism and psychopathy among women is absolutely terrifying, because the potential for modification is I think three, four times higher among women than among men. Mm-hmm. Sam, if we still have time, how NPD, if he or she can cope with mortification by himself or herself, is it possible? Yes, if you don't commit suicide, if you survive the depression, the internal solution will kick in automatically. The internal and the external solution. The solution is described by Libby. These two solutions, they're automatic. It's not a decision, it's not a choice of the narcissist. They kick in automatically. So you have just to survive the period, you have to survive the period where you are very depressed and anxious, humiliated and ashamed to the point that you want to die. So you have to survive that period. And if you survive it, then your grandiosity will be restored, your false self and so on. So during that period, the narcissist is a borderline, and the chances for suicide are in some settings up to 60%. It's very, very traumatised borderline. And I have another video where I analysed the situation there with studies and so on, so about 62% chance of suicide. It's not small, it's very, very dangerous. Sam, last questions. You are speaking a lot about, you know, different emotions, but mostly about shame. Why shame is associated with mortification? Why this one? Shame? Well, first of all, mortification involves being humiliated or being ashamed in public. Yeah, but you know. Shame is the main emotion in narcissism. And many, many scholars like Morrison and others, they think that narcissism is defence against shame. The child, the small child is made to feel ashamed, made to feel insufficient, inadequate, love is conditioned on performance, and very often the performance is not enough, and so on, so forth. So the manipulation of the small child, who later becomes a narcissist, consists of shaming the child somehow. And the child accumulates this shame a lot. The child is also ashamed that he cannot become an individual. The parental figures don't allow the child to separate and individuate, don't allow the child to become a person. They breach the child's boundaries. They don't respect the child, in other words. Abuse is a form of disrespect. So abuse causes a lot of shame. That's why victims very often don't complain. They don't complain because they feel ashamed. They feel ashamed of their victimhood.  He grieves what he could have been and would never be. And he grieves the way his parents treated him. So there's what we call long grief. Long grief and shame. When modification happens, the narcissist gets in touch with his shame because all his defenses disappear. He suddenly feels like he's a two-year-old with huge shame and nothing to do about it. He's helpless and he's hopeless. And there is this overwhelming sense of grief, mourning. And then there's a question, what am I grieving? If I'm a narcissist, I've been mortified. I'm depressed, I'm anxious. I'm in touch with my shame and I'm grieving. What am I grieving? I'm grieving myself. I'm grieving myself. So if I'm grieving myself, I'm already dead. That's the big lesson in realization of mortification. Suddenly the narcissist realizes that he is dead inside. That he has never lived. There's never been a life there. So he says, all my life has been fake. I've always been dead. Let me die.  And that's if mortification is not, you know, for example, if the narcissist is lonely, there's no family, no friends, which is the typical case when the narcissist is much older and so on and so forth, the chances of suicide are enormous, absolutely enormous. So even if you don't like a narcissist, even if you think many times before you humiliate or shame or attack a narcissist in public, because you may well be condemning him to death. And yet there are many narcissists deserve many punishments, but I don't think death is one of them. Sam, thank you so much for explaining this for us because like I said before, it's really difficult topic and it's a lot of misunderstanding. And so thank you so much for your time and it was nice to talk to you. Yes, nice to see you again. Thank you for having me. Thank you so much. Take care. Bye.