So my name's Amy. I was just, I want to share a little bit about my own personal story, my own personal testimony and how the Lord has done a great work in my life through this personal way. So I grew up in a Christian home. Pastor Wayne was a pastor my whole life. I grew up in the church pretty much born, I was born on Easter and my dad gave his message that same day, Easter morning. So I I know what it was like being told about the Lord from a young age and I felt like I really had a tender spirit towards him. As so many kids do, which I love so much how the Lord uses family to raise up kids in him to share that truth about him. About the Lord and as a young child I gave my heart to the Lord probably about five five or six years old. I remember being, I remember writing my first song about the Apostle Paul when I was like eight. Actually it was a rap so that's kind of cool. But I also knew that I had a rebellious heart and a rebellious nature inside me. I could sense that from a young age. I remember stealing money from a girl when I was like 10 years old. I just like remember it vividly in Sunday school. Like that's so I mean pastor's kids, I carried the stereotype pretty much of the rebellious nature and that was just in me.  I was in me, I was in my heart. And so I knew that I knew that God, I knew that I had to find my own relationship with the Lord. I had to choose Him and open up my own heart to Him as I got older, as I became my own person, became an adult woman, somebody who had the mind to make that choice. So an important part of my testimony and how the Lord has worked in my life, I want to compare with what I do today for work. I'm a nurse in the ER and so I see a lot of patients come in of all many various issues and needs and sicknesses and problems that come upon them without announcement. And the three things that I've seen is that patients come in in a very vulnerable state in a very large time of need.  They don't plan it. They don't prepare. They don't get all looking good for it to come in. They just come because they have to come then and they trust. So they're vulnerable. They come as they are. They have a need and they trust that we're gonna do what it takes to take care of them. What we're gonna meet their needs and they 100% have to put their trust in us. So in my own life, I've seen this take place as I was growing up and in my high school years, I grew up pretty much a big tomboy. I had three brothers, an older brother who I very much admired and wanted to be twins with and cut my hair like him and wore his clothes and you know, everyone asked if I was a boy and my mom tried to put pink boots on me and dresses with apples and all this weird stuff. But I didn't appreciate that. But you know, now I dress a little more girly but at the time, you know, I was I just identified more with that and I was really into sports. I ended up having a very successful basketball career, played all through high school and college, played professionally over in Europe for a year and had a tryout with the WNBA after college. That was a huge passion and it was a huge piece of my life just because it opened up opportunity to get school paid for. I loved it. I had a passion for it and I was good at it. And in that time, I found myself in relationships where I became confused about and just trying to search out my sexuality.  You know, I just found myself real connected to people that weren't necessarily in my Christian circle. And again, that's just like I love being friends with all kinds of people and I think we all should. I don't think we should all be stuck in kind of our our own Christian community, although that is what God uses to strengthen us and be there for each other. But I sense that I, you know, how to I want to I want to be in different types of circles. So I found myself in this relationship and and then from there, you know, that kind of began my struggle in the homosexual lifestyle. So through high school and college and at one point in college was in a relationship with a gal for over a year and really loved her and was very much like wondering if this was who I was. If I was gay, if God, you know, made me this way and just struggling with those questions that I think people just face because you think that this this feels right to me, I feel happy. But at the same time, I felt I felt that unrest in my heart and that disturbance of my peace. And also in my relationship with the Lord, I felt not that he didn't love me. I knew that he loved me. He kept me. He kept a tender kind of my heart tender towards him. I never hardened it in the way where I walked away from my faith and I'm so so grateful for that. And that's only by his grace. But you know, I knew he loved me, but I knew that he wanted me to walk away at some point. So I had to be vulnerable before God. And at the time when I was first struggling, it was really, really hard. And I was dishonest a lot about it. I tried to, I wasn't totally honest with my friends with myself. Really, you know, lied a lot about it and then came to a place where God really broke me down and really had, I had to be honest with myself. I had to be vulnerable before God and know that he knew me well enough to know that I was going to go through this, but also know that I had the strength through him to walk away if he was give, if he was putting that tug on my heart and he was. And I think that God does that through, through his Holy Spirit, through, through that conviction. So I was vulnerable before him. I had to see my need just like somebody when they come in to see us in the hospital, they have to choose to see it.  And I had to see that for myself. Just like I was saying, growing up, we all have to choose the Lord at some point for ourself. It's nobody can choose it for us. People can obviously be a huge influence in our life. And that's how, you know, we all have a story of how somebody has shared the Lord with us. But I had to see that need within myself. And I think that specific issue today and issues of sexuality in general and just identity and who I am and who I was born as and who I was created to be, you know, people think that, oh, just do what makes you happy or do what those desires that you have, don't suppress them. You know, and I think to a certain extent, like, there is some truth, but God created us and he made us his masterpiece, you know. And if we want to follow him, we have to trust that our identity is in him and not in something even like that.  That's not all of who I am. Just like when somebody comes in with the need, that's not the only thing that is about them, you know, and God knows that God knows how to meet those needs in his best way, which is why he did create marriage and he did create a way for those needs to be met for us, for us to have abundant life in him. And then the trust factor, I had to really, so once I made the choice, I knew I had to walk away.  Like, I was, I don't know. I, for me, it was just like, it's not like it was a temptation everywhere, but in certain situations, I was just like, it would kind of catch me off guard and that's how sin is. You know, we can't just think, oh, we're above it and oh, God just, you know, all of a sudden you're healed from this thing. I mean, that's not necessarily true. It requires dependence and faith in him.  You said this is, this takes, this strains our relationship. And I've seen that a lot with people that I know, you know, that God slowly but surely becomes more distant in their life to a point where he doesn't factor in anymore. And I think Satan uses that with certain sins and lifestyles and different things just to pull people away because it just happens over time. You just can't deny it, you know, so you have to keep that conviction from the Holy Spirit and make that choice. And you have to trust that God will meet your needs in those ways. You have to be patient and trust. It's not just this some immediate, you're healed from this thing. You know, God is constantly restoring us and our broken identities and, and, you know, what we want to do in our flesh to make us more dependent and have more faith in him.  And it's not even totally about that. People are like, Oh, you know, how can Amy be straight now?   And it's like, well, you don't know what God's about. It's not even about that to me. Yeah, those are, those are innate desires. And I need to constantly be on guard and have good boundaries in my life and, you know, continue to surrender things that could be stumbling me. But it's about God providing and his provision and faithfulness in my life to where he did meet that need through one, one special person that he knew would be a perfect fit for me in that way. He knew I had a desire to be intimate with someone and have a, a partnership and, and a marriage and to have a family and all that stuff. He knew that. And also, all I had to do was stay vulnerable, come as I was and trust him. I don't, you know, people can be struggling where they're at and, and they can still surrender it to the Lord. They might not be like totally over, you know, walk away from it at that point. And that's where we come in as the church, you know, to love people and to walk alongside them in issues such as that, you know, you can't just say, come on, turn from it. It's wrong. It's, it's bowed out every verse. Although those truthful verses in God's word are so great and it's so important. I would never try to downsize the importance and impact of God's word, but also that's where love comes in. He says, without love, anything that we do is nothing. It's worthless. And that's where we have to walk alongside each other when people are navigating through these kind of issues and be sensitive and gracious and also pray for the spirit to do that work in their heart and, you know, you can't force it. That's somebody's personal choice that they have to make. And I just believe that God wants to restore in those communities and sexual identity and, in other types of real deep inner issues that people are going through and hopefully bring people to an understanding that our identity, when they choose to follow the Lord, that our identity is in him and it's not in anything else. Everything else falls into place as we seek with our lives to serve him, to put him as the king in our life where he needs to be.  So I know that he's done that in my life. I've seen how he loves to do his greatest work in the times of people's greatest difficulty, whatever it might be, something that's happened to you or something that you've chosen. It doesn't even matter. He does his greatest work when we just surrender that to him, are vulnerable, come as we are, see our need for him and just trust and wait on him to do that in our life. So that's a little bit of my story. I appreciate you guys listening. We're going to spend a few minutes here in closing to look into God's Word. Turn to Luke chapter two. What we're talking about today is that God is faithful and we're talking about how he redeems things and he redeems people. He especially loves to rescue people out of their bondage and their darkness and brokenness and messed up lives. That was us. That may be you still. Jesus wants to take Humpty Dumpty, put him back together, but make him brand new. He wants to heal our lives and change our lives. Even music, he can redeem. He did it throughout the Jesus movement. It's interesting, back in the 1600s, you know there's always been winter solstice type celebrations. There's always been that. Dating back thousands of years. We don't even really know when Jesus Christ was born. Doubtful that he was born on December 25th. That's a day we choose to acknowledge the incarnation of God. Think of that. That's worth celebrating. That's amazing. But people used to celebrate Saturnalia. And they've been having these winter celebrations, including Christmas for a long time. In the 1600s in England, the winter celebrations became so riotous and so raucous. There was so much drunkenness and violence that the Parliament of England actually closed down winter celebrations. They enacted laws saying you can't do it because it got so dark and so bad. But then God was working. God was working among real Christians who loved the Lord and Christmas carols began to be written. And these songs started coming to light and they started praising God for Emmanuel, for the coming of Christ. And these Christmas carols became a part of praising God for the coming of Jesus, the Messiah, the Savior of the world. And it became this thing that changed people's winter celebrations. And the Parliament just realized, you know, people are having these celebrations and they're so full of peace and joy and they decided you can do it again. Why? Because Christ changed it. Christ changed it. That's why we should keep Christ in Christmas. What do you think? Now, Luke chapter two, Luke two one, Luke's version of the birth of Christ. And it came to pass in those days that a decree went out from Caesar Augustus that all the world should be registered for the census to be taxed. This census first took place while Corinius was governing Syria. So all went to be registered, everyone to his own city. Joseph also went up from Galilee out of the city of Nazareth into Judea to the city of David which is called Bethlehem because he was of the house and lineage of David to be registered with Mary, his betrothed wife who was with child. So it was that while they were there, the days were completed for her to be delivered. And she brought forth her firstborn son and wrapped him in swaddling clothes and laid him in a manger because there was no room for them in the end. Heavenly Father, you invite your Holy Spirit to speak to us in these last minutes of this service using your word, God, right where people are at, touch their hearts, speak to them, open them, each of us even more to what you have for our lives. In Jesus' name we pray. Amen. So Jesus' birth took place when Rome's greatest emperor was in power, Caesar Augustus. His original name was Caius Octavius. He was Julius Caesar's favorite nephew. He was a very, very powerful emperor. It is said that he changed the city of Rome from a city of stone to a city of marble. And so people were impressed by this man as such a powerful being. They said he should be called Augustus, which means reverence or of the gods. And so here the ruler of the Roman Empire, who's sort of viewed as a god, was in power when the true God was born as a man in a little village hundreds and hundreds of miles away. Of course the Jews were so opposed to the Roman oppression and to go from your present town to the city of your heritage to be registered for taxes. Oh, I mean they hated the Roman taxes, kind of like we may feel about the IRS. But you know God even uses oppressive obnoxious things to work on behalf of his people. In fact he causes all things to work for good to those who love him and are the called according to his purpose. And God's purpose was that the Messiah, the Savior of the world, will be born in a little town of Bethlehem because seven years, seven hundred years earlier Micah the prophet had said, but as for you, Bethlehem, afraid of too little to even be numbered among the clans of Israel, from you one will go forth to be ruler in Israel, whose goings forth were from long ago, even from the days of eternity. And he will be the one who will shepherd Israel. That was God's plan, but they lived in Nazareth, but God took an emperor who is a mere pawn in his hand. Presidents are pawns in the hand of God as far as his ultimate plan. They're not the ones that can change our lives. They can't save our lives. They're not our protectors and our providers. God is. Amen. Yes, and we have a calling to love and serve him, let him care for us and us do his bidding and bring out his message. When he looks down on this earth, he's looking at the church, his bride, his people. You know the guy that was really the one who was really running the show was that little baby in the womb of that woman riding on the donkey 80 miles over mountainous territory to get to Bethlehem and she was, you know, ready to give birth when she got to Bethlehem because that's God's timing. It was his plan. It's surprising she didn't give birth on the way down with the bumpy ride that they were on.  Watch out, you know. Really? But it is inspiring to see a pregnant woman jumping around, isn't it? She's fairly athletic. Okay, but listen, people, sometimes obnoxious things are going on around us. Things that are oppressive, things that what's going on. Lord, we don't understand it, but you know what? This we know, he loves me and he has a good plan for my life. The plans he has for me are not for harm and evil, but he said to Israel, put there for good and to give you a future and a hope. And the same is true for us who believe in Jesus. Amen. So we can trust him and see what he will do because he is faithful. He needed to get that family down to the city called the house of bread because the bread of life was about to come out of the oven. Amen. And we all needed to partake. That's the bottom line. Speaking of food, he was taken and placed in a manger when he was born.  When you go to Israel, like David has gone many times, I've gone many times. The manger is like a stone that's been carved out. It's a big stone thing. It's not those little wooden things, but it's a big stone thing. They took him and they put him there where the animals would eat. You'd think, wow, why a stable? Why not the room at the end? And then it says they put him in the manger wrapped in swaddling clothes.  You wrap them tight because they need that sense of security and comfort. They've been in a tight place and they come out and here's the great big world. Ah, you know, I mean it is a little freaky out here. Come on. And so they're swaddled and they feel, make them feel comfortable and good. But you know, it's interesting the swaddling cloths it says. That word is used by Dr. Luke and it's the same word. It's actually a medical word that also means bandages, bandages. And it was also the word that was used for wrapping the dead when someone died. It's kind of a hint of why Jesus came. Because he came to a hurting world. He came to a world filled with spiritual death. And he was wrapped but he came to bring not a bandage but the cure. The cure for our illness. To the illness of sin which was breaking and destroying our life and had brought death and he came to die. Amen? That's why he came. He was the only person ever born for the purpose mainly of dying. Because he came to pay the price. The wages of sin is death. Every one of us will either die eternally without God or we'll put our faith in the one who died for us. And we'll be given the gift of eternal life by him. That's our choice and he wants you to receive that. That wonderful gift. He wants to make you whole. The great physician like Amy said so well. Coming in just as you are. Vulnerable in need trusting that the great physician is the only one who can heal you. Doctors can't heal every aspect of your life. Thank God for their talents but the great physician, he's the great healer. Now one last thing and to me this is the most interesting part of this message and maybe you haven't heard this. It could be a new concept but it talks about the inn. We all know about that. It says that he was laid in a manger verse seven because there was no room for them in the inn. So they came, they asked for a room and they didn't get it. Now this room that they were seeking may have been a place with the long Bible history of hospitality because a thousand years before Christ when King David was king of Israel, remember his son Absalom conspired against him and stole his throne and so David fled from Jerusalem and he went across the Jordan River and he hid in the land of Gilead east of the Jordan 60 miles away. Now while David was there he made a close friend with a guy named Barzali. And Barzali was this tremendous wealthy old landowner, a Gileadite and he took David in. He befriended him. He said, I'll take care of you. I'll supply your needs and the needs of your men and your cabinet. David was so appreciative of being taken in. Well when David was re-enthroned as king of Israel he asked Barzali, okay I'm going back to Jerusalem and re-establishing my throne and the cabinet. I want you to come with me.  He likes his home in Gilead. He doesn't want to travel you know to some place and and you know he's 80. When you're 80 you kind of want to be comfortable. And and he's like no I don't want to go but here's an idea. My son, Chimham, he needs a good job and I'd like you to consider him.  He's got a lot of talents. He just needs an opportunity. Will you take him in? And according to 2 Samuel 19 this whole story, read that. David said okay I'll take your son Chimham and Chimham from then on became part of David's inner circle. Now sometime later we know that Chimham built a lodge or an inn. He built like a hotel near Bethlehem and he called it Gareth Chimham which basically means Chimham's inn. Evidently that same spirit of welcoming, of hospitality, of caring for the needy, he established it as a lodge for traveling people that maybe we're going through you know difficult travels and different things and they could stay there and they could be refreshed and relieved. It's interesting because if we fast forward then 400 years in Jeremiah's time. Jeremiah during the time when there was such turmoil and captivity from the Babylonians, he was taken to Egypt and they stopped at this place. Chimham's inn and he we know was the weeping prophet. He didn't have much relief in his life. I mean he started with the church of thousands and the more he preached the less people there were. He got it down to zero. Now that hasn't happened to David so we really praise God for that. It hasn't happened to me but he had this difficult calling because they were called to be exiled. To be taken away because they were so rebellious. But he stopped at that inn and it says that he received refreshment and blessing in Jeremiah 417. Now it's interesting that the name Chimham means pine and it's kind of just interesting in passing. Not pine in the sense of a tree but pine in the sense of sadness, pining. Now you pine for someone, you miss them. Maybe they've left, they're gone, whatever you're pining away. That's what it meant and while Jeremiah was pining and sad, he received comfort and refreshment. It's very possible that 600 years later that same inn may have been the one that Joseph and Mary came to looking for a good reception. It had that reputation for hospitality, for a welcome. She needed that. She was nine months pregnant. Joseph I'm sure pleaded with the innkeeper. Please don't you understand? Look at her she's pregnant. I mean we she's about she's in labor man. He'd help. Oh sorry. Don't have any room but there's a place for animals out there. There's the stable. Try that. You know the innkeeper it's possible because this happens in that part of the world where descendants take the occupation of the one before them. It could have been a descendant even of Chimham and Barzillai who said no we don't have any room. Unfortunately he didn't really show the same heart that his forefathers had shown and that's not uncommon. Just because someone's a believer and loves the Lord doesn't mean their descendants or their family is going to have that same attitude. Now a person might say well how could he give them a room there was none available. Don't you understand Wayne? All the rooms were taken. Wait a second. Wait one minute. There was one room and that was the innkeeper's own room. He could have given them his room. Barzillai would have given his room to David and he did. Chimham would have done it and think if this innkeeper would have done that and in his own room his own part of the hotel his little what do you call it you know apartment would have been the birth of the king of all kings and the savior of the world. Think of that. Think if if he would have opened his door and said okay yeah you can have ours I'm getting plenty of money because of all these other people I'll find another place and you know but you can have ours it would have been his house where the angels would have come and and said behold I bring you glad tidings of great joy for unto you this day is born in the city of David a savior who is Christ the Lord glory to God in the highest end on earth peace and good will to he would have done it right there in his house in his room in that place the glory of the Lord would have filled that place and shown all around about his family and he would have been the first witness of the Christ child but instead he says oh yeah no sorry I you know we we're all filled but there's a stable for you no wonder the first witnesses were shepherds all of it happened in the middle of the night he needed comfort he had his warm bed but the greatest event in history was happening without him even knowing it not far from his doors he didn't have any room for the Lord of glory but what wonders he missed out on when they had been directed right to him right to his doorway I think it's something challenging to think about you know because God brings opportunities our way every day in fact the Bible says you know if you take in the hungry if you take in thirsty people if you share a cup of cold water or you know a meal or something but someone in need if you if someone's in prison they're in bondage to something and you say here's how you can be free and Jesus uses you to help free the captives you've done it to me he said you've done it to me he didn't want to be bothered but he missed out I don't want to be cheated out of the wonders God wants to do in and through my life these are opportune times we're in you see the room that Jesus wants today it's not just any old room he wants your room he wants your heart number one and he wants yes your house he wants your life your family he wants your space to show his glory this is the exciting life this is the joyous life I don't care how old you are I'm 65 and I believe God still has great things for you amazing I don't care how young you are God is doing stuff and he'll do it in and through you now you may not know him yet you may not know this God of wonders you know whoever the innkeeper was he thought no I don't I can't this is bad timing it's not convenient you're going to alter the whole thing here yeah your life is going to become an altar buddy that's how it is when you have Jesus he does alter your life but it's for good it's for joy man he had listen to this by grace are you saved through faith God's grace his love not of yourselves it's the gift of God not of worksless anyone should both for we are his workmanship created in Christ Jesus for good works which God prepares beforehand for you to walk in that's the exciting life you open your heart by grace you receive salvation as a total free gift and then he has a life that blows your mind a life of opportunity of blessing of joy because you're making room for him and he is there to do amazing things now not every day's a thrill a lot of times it's just steady walking with it but you never know and I would say every day he's prepared opportunities for you to walk in to share but you have to keep alert this guy was blinded to what was happening he missed it I don't want to miss that I don't want my life to be wasted I don't want the biggest and best opportunities that might come along for me to say no you know here let the sheep have that no wonder those cattle were lowing so hard you know the sheep buying and everyone praising out in the stable what an amazing time this guy I think he's an example to us God has things for us let's open our hearts open our houses open our lives fully my family by God's grace and God's grace alone every single one of them loves Jesus is following the Lord and serving him they had their days of wild oaths God brought him back in the fold and they he will for you have faith trust him pray for them kids they're gonna come back but show them by your life that it's worth it your life is still 100 for him don't tell him how great the Lord is when you're 20 for Jesus they don't see it so the Lord is calling us to open up and give ourselves fully


Okay. Good morning everyone. My name is Xiao Yilu. I come from the Ohio State University. I'm a research scientist doing the research in big data and cloud computing. So today I'm so happy to present this talk here to my region because so many of you come to listen to my talk. Thanks a lot. And first of all, I apologize that my co-presenter, co-presenter Dr. D. K. Panda, because of some personal constraints at the last minute, he couldn't come. So I will present the whole talk. So this talk is about accelerating big data processing in the framework provisioning with OpenStack, heat-based, Hadoop, and Spark. So these days, I mean, all of us talking about big data, which is a big problem, a lot of challenges. The main reason is because the data is growing so fast. For example, let's say every day when we clicked our website, we use our smartphone or our operations, we generate data. And this data needs to be stored, analyzed, and processed. That's why big data becomes a big problem. And actually this problem is not only occurred for industry or business domains. It's also happening for the scientific or research domains. Let's say this days a lot of scientific big data problems as well. So to some extent, big data becomes like the speed of big data growing. These days, we see it almost faster or higher than the more slow. So in order to process this big data in a fast and scalable manner, a lot of people start trying to converge big data and high-performance computing technologies to meet these type of challenges, to solve these type of challenges. And on the other hand, running high-performance data analytics workloads on top of cloud is also gaining popularity. Let's say, according to the latest OpenStack survey, around almost 30% of the cloud deployments are running HPDA workloads. So when we talk about big data, so if you look from the system perspective, what kind of solutions or what kind of technologies these days people are using to solve big data problems, to run big data applications. So broadly, we define into two tiers. One is the frontier, one is back-end tier. The front-end tier is just like the example I mentioned earlier.  They say web server, like a database server or long-sigo DB server, kind of things. And then this data will get stored, get processed there, and then it also go back to the back-end storage. Here we give example like HTFS. So probably you can also use SAF or orange GFS, some other kind of fire systems. And then on top of that, people typically run some kind of machine learning, data mining, deep learning kind of workloads on top of it.  So how many of you familiar about MapReduce? Can you please raise your hand? Okay, great. There are so many people familiar with that. So just let everybody in the same page, I just quickly give some high-level view of what kind of ideas of MapReduce so that later on people can understand my talk easily. So broadly for MapReduce, just like here, the diagram shows, you have a big problem. You're written with some user-level program code. And then there is a kind of master-worker kind of architecture. And then this program will launch, and the master will assign a task to different kind of data splits. And then you run map tasks on each of the split. And then the output of a map task will get shuffled to the reduced phase. This is the reduced task. And then this map output will get gathered and aggregated, processed, and then output to this real fire system. So this kind of defined conqueror architecture. So during this phase, a lot of problems can get solved in a four-tolerant and scalable fashion. This is just like an example. You have a lot of tasks to do, to be done by yourself, but you have a lot of friends, good friends. So one way you can do is, you can do by yourself, which is sequential manner, which is not scalable, which is not high performance. But you can also assign your tasks to good friends, right? And then let's say you have 10 friends, and each of them help you a little, then you can get, like, ideally you can get a 10 times improvement. That's some example behind the map reduce. This hopefully is easier to help you to understand. Okay, this is for map reduce. Let's take a look at the concrete example. Like, here is work count. Let's say you have, if you have this file, this file is small, so you can write any kind of program to solve it. But think about if this file is like one terabyte or one petabyte. If you want to do work count on this file, then this problem becomes hard, right? Especially if you consider about four tolerates, okay? Especially because if some task gets failed, then how you handle it properly. So like I said earlier, for example, the flow of map reduce is like this. So you divide this file into multiple splits or partition. And then you run your map task. Each map task will take over one file and process on it. And output gets shuffled to the reduce phase. And then you reduce these dual aggregation and output in the HDFS or other final systems. So in this way, the huge problem becomes to the simpler problems and they get solved. Okay? So this is the idea behind that. Why these states are so popular? That's the one reason of making problems solved easily and fast and also scalable. And another perspective is about productivity or programming. Think about if you write this word count example by yourself. If you use MPI, PEGAS, or other kind of language, you need to write a lot of code. Especially if you want to handle one terabyte, one petabyte, or one zetabyte of data. But for Hadoop map reduce, these states, you can only write 63 lines of code. Okay? The same code you can run on any kind of data sets without any changes. Okay? That's why these states Hadoop is so popular for especially for the developers or engineers who is trying to do some fast, like ideal implementation and see the result, how the result come out and trying to change their solution. So, and also like I said, it can be run scalable manner and for tolerant productivity. Okay? This is the Hadoop. So, some of you may also familiar with Spark or heard of Spark, right? Now, this example, same example, becomes even simpler in Spark. How many lines now? Three. Okay? So, that's why Spark is getting momentum these days. A lot of people trying to use Spark. Okay, this is one of the reasons. See, you can easily define your file in HDFS. You can also change it to take care of other file systems. Okay? This is your Spark file. They say RDD. If you some of you heard of this concept. And then you can do like a based on this file, you get each line and then do a split. And then you just counting the occurrence of each word. And then you save the output to HDFS. So, this idea of the Spark. You get three lines. This code is all very even more productivity you can get. And then it's scalable, for tolerant, as well as high performance. Okay? The high performance, the reason of high performance is because this Hadoop is being developed or designed for like batch processing. But in many scenario, your workloads maybe iterate, you have it, you will run iteratively, right? And also interactively. So, Spark will save all this data or RDDs in the memory. I mean, so that you can repeatedly run your programs on top of it. So, let me give an example. Another more concrete example or complex example. World count is too simple. Maybe some of you say that, okay, that doesn't mean anything. Right? Now, let's take a look at log mining. So, let's say, if we are developers, we always want to do what? We have, we write our code. We see some arrows. We are trying to debug. Or you're trying to see what kind of arrows, what kind of problem happening behind the system. So, one way is like do log mining, right? So, typically when we do log mining, we can use NITIC share, we do grab, we do like card or sort kind of things to find what's the problem actually. And then in Spark, they say how we can do it. When we think of this scenario, think about your data is huge. Not only one file. You have like thousands of tens of thousands of files stored in your cluster. How do you do that efficiently? Okay? So, this is the architecture of running Spark applications on top of your cluster.  And then first of all, you say that, okay, where's my file? You get the file from the HTFS. And then we call it base RDD. Can load it into memory. And then just like we do grab, we do like we say, okay, for this file, we just want to select the lines and each line starts with arrow because we're trying to see what's happening for the arrow part, right? And then we call it transform RDD. And then after that, we say that arrow is just a tag, right? We actually want an arrow message. So, we do a split. We get an arrow message from the second field, let's say. And then because we want to find the reason, so it may not just run around, right? We want to repeatedly to analyze this data. So, we want to cache this data into the memory. So, the next time I run some other commands or run other some instructions, it can run in memory speed. So, we do a cache and then now we want to see how many times or how many lines related with this type of event or anything else you can define. And then we do a count. So, now let's see how this gets executed. So, then Spark will get these lines and then he's trying to submit the jobs to the cluster, okay? And it's like a MapReduce. This task will be assigned to different nodes. And each node will take a piece of data and analyze for you, okay? This is like a scalable. And then get the results back to the driver program and then you get the output, okay? You get the results. So, this is how it gets executed. This exactly like a MapReduce, but the interesting part is the next one. So, because we say cache, okay? So, this output or some earlier phase results can be cached in a memory. And the next time we want to say that how about another message or like a bar or anything else you can you can you want to you want to search or you want to analyze. So, the second line, this one will be executed in the cached dataset so that you get much faster than Hadoop, okay? So, this is like a design principle or ideas behind Spark. Let's just give some high-level results. Let's say based on Databricks numbers they say that a full-text search on Wikipedia data around 60 GB on 20 EC2 machines is only about 0.5 seconds compared if you do this search on top of disk. On top of disk is about 20 seconds, this 0.5 second. Think about if you can whether you write other programs you can do like 0.5 second full-text search on Wikipedia data. Okay, another one, the same program can scale to the 1 terabyte of data in about 5 to 7 seconds, okay? But if you do on disk is about 170 seconds. That's the idea of memory computing these days. People are trying to bring into the data middleware. Okay, so this is just some background overview so that people can understand what I'm going to talk in this outline, okay? So, I want to tell you guys what kind of challenges of making this processing parallel even faster with HPC technologies. What kind of bottlenecks are there, okay? And then I also want to introduce what kind of work we have done in our group. We called a high-performance big data project, like short for high BD. And then we introduced some kind of basic designs, like going deep, what kind of designs we can propose with high-performance networks. And also because this big cloud community, right, we want to see that what kind of opportunities we can further optimize for bigger libraries on top of cloud. So, we are going to introduce something like a cloud where we already have the processing, okay? And then in tomorrow's talk, I have another two talks. In tomorrow's one, I will introduce how to bring our DMA technology into OpenStack Swift to make it even faster. And then we also want to say that because in cloud environment, how to deploy your application as fast as possible is another big challenge. So, thanks to the OpenStack community, the heat component, we think it's very useful to help us to deploy this whole stack because you see big data everywhere, so many layers from the under this one to the like a fire system, to your MapReduce, Hadoop, your two applications, so many layers, so many dependencies, how to deploy it efficiently, right? That's a big challenge, okay? Now, let's take a look. What kind of opportunities first in these days, especially for high-performance computing domain, high-performance cluster or cloud architectures. So, whenever we go to HPC cluster or super computer these days, we see every node is multi-core, many core kind of technologies. You have very high-performance Xeon cores or Xeon fine or GPGPUs. And then also these days, you have a lot of memory or large memory nodes, one terabyte of memory nodes, also very popular, right? And also SSD, MVRUN, parallel file systems, and object storage, this kind of different storage technologies also available in the cloud and also HPC clusters. There's another two important technologies I want to introduce here. One is RDMA-enabled networking. Two examples, InfiliBand and Rocky. How many of you use this network? Okay, a few of you, okay? Another important technology is we call the Thinkaloud IO virtualization. How many of you have heard of this? Okay, a lot. Good, that's because we are cloud. Okay, so let me introduce these two just in two or three slides. In this slide, we're just going to overview or summarize what kind of communication protocols or what kind of communication mechanisms or network you can use these days in your HPC cloud or HPC cluster. Okay, from left side is the one we are very familiar, like TCP-IP, over-resonate, over-resonate driver-resonate adapter, and this is a switch, right? We start learning this from when we are students. So these have been used in many, many domains, like all the big data middlewares these days if you see everything developed on top of Sockets and then running with TCP-IP stack. But if you take a look at the right side, the right side is something, it's very exciting because it gives you much, much faster performance than the left side, which is called RDMA technology. I will introduce what is RDMA later. So basically, it doesn't use Sockets API anymore. It will use verbs, APIs, and then it will use RDMA technologies and go through the user-level communication protocol and running with InfiliBand adapter and InfiliBand switch. Okay, so this will give you a lot of benefit. What kind of benefit? Let's take a look at these slides. So I want to introduce a little bit about why RDMA is important these days and why it can give you good performance. Think about the center receive. First, before I introduce RDMA, center receive means what? Receiver side posts the receive. Center side posts send. And then the network communication for you and then in the receiver side do a match and go to your memory, right? This is like a two-sided communication. Each side needs to be involved. That's why you cannot achieve best performance, okay? Because each side needs to be involved. There are CPU resources, a lot of things it needs to be participating in the communication process. Now somebody, some smaller guys say that, okay, can we do one-sided communication? Okay, if I if I know I want I will communicate with you why I cannot directly write the data into your memory? Because in the single node you probably heard, I think all of us should know RDMA, right? RDMA means what? You write into the memory without CPU involvement. And then somebody said, okay, can we do this in a remote function? I can write to somebody which I trust or you trust me. I can directly write to your memory so that whatever you're doing, you continue, right? You don't have to be involved in the communication process. That's called one-sided communication or RDMA technology. Okay, now let me give an elimination. So let's say this is center side, this is the receiver side, okay? So the center side, I'm trying to send the data to the receiver, okay? This is the data in the memory and then the infinite card will be smartly take your data directly right into the remote memory location, okay? So this is called remote direct memory access, okay? So that in this and the hardware acknowledgement everything will be handled by the NIC, as well. So take a look at this phase. The initiated process is involved only for post-send descriptor and also pull out the complication queue from the complication event from the complication queue, right? But for the receiver side, the CPU is not involved at all, okay? So this is the major idea behind RDMA. Okay, so if we want to bring these technologies into cloud, another technology is needed which is called single-route IO fertilization, SRV, okay? The idea is that because earlier, if we are familiar with IO fertilization or networking fertilization, typically we do what? We do front-end driver, back-end driver and then we do the software-based kind of fertilization, right? That's good, but like you lose performance. The reason is because each package you need to come back and forth from different layers and then there's a lot of overhead. So in the community people trying to solve that problem by proposing single-route IO fertilization, this gives a lot of new opportunities to design high performance communication IO middleware for big data and other workloads. The basic idea is this. So now this if the uniband card or other SRV supported PCI device can present itself like multiple virtual functions in the hardware layer, okay? And then the hypervisor when we when we launch the virtual machines, and we can select each of the virtual functions and then map it directly into the guest OS. So that this guest from this guest OS perspective, it seems like that it can dedicated use the hardware directly, okay? That's why SRV give you a lot of opportunities because the performance can improve a lot, okay? So in Fitiband now these days also support SRV technologies and also other kind of high-performance Ethernet like a pancake or 4G Ethernet. So with this let's take a look if you want to build efficient cloud with SRV and the Fitiband. In Fitiband or high-performance networks like ROCKY, IWARP give you a lot of opportunities for good performance. There's a low latency, few microseconds now these days, and the high-band ones. With the Fitiband HDR card you can achieve 200 gbps these days, okay? And the fairly low CPU overhead like I said because the remote side or the receiver side the CPU is not involved in the in the receive phase, right? So that you only need like 5 to 10 percent of the CPU involvement. It gives a lot of a chance to do the overlapping of your complication, complication and IO. And then all of this like open fabric software stack like O-FIT is very popularly is very popularly used in many HPC systems and also is open source. People can use it directly. Now the question is how to build the efficient clouds with SRV in Fitiband to deliver near optimal performance or near variable performance in your cloud. That's the overall problem we want to solve in this talk. And then particularly for big-data midwars. So we want to solve some kind of challenge like this. So these days like I mentioned earlier big-data midwars by before they are developed and designed with sockets, TCP and IP kind of complication protocols. But because RDMA is showing so good features or so good performance why we cannot use it. But the challenge is what? Our design is written with sockets. It's using standard default Java libraries or something like that. How you can use verbs. Right? That's some of kind of challenges. And also we have these days not only DRAM based the complication. These days like MVRAM is also available. What kind of MVRAM based aware complication IO schemes can can help and how to use like a different kind of SSDs, SATA, PCIe, NVMe, Parallel 5C support, Optimize overlapping, different thread models and the singleization and the locality aware designs. Because in cloud a lot of different layers like virtual machines, containers, your tasks is no longer just running on top of native nodes.  You have to aware of the underlist architecture or underlist network topology. And for tolerance, residency, efficient data access placement, efficient task scheduling, fast deployment or kinds of issues. We want to see what kind of designs we can propose. Okay. So this slide showed that what kind of challenges we have we have addressed so far. So these applications, this big middleware, we have do a lot of designs with HDFS map loose spark, HBAS memory cache and extra. And then in this layer we call the resource management scheduling systems for cloud. Like OpenStack, Swift or Heat kind of systems. Definitely normal. Those components are there. And then for the communication, the LIO library, the most important thing is already made in SRV. How to utilize that? How to get better designs inside a big middleware. Locality aware communication, virtualization, data placement, kind of things. Okay. So now let's take a look at the concrete designs or concrete things we have done in our group. So this is just overview of what we have done. So first of all we take Hadoop and Spark as examples. We optimize that with RDMA technologies. We have developed RDMA for budget Spark, RDMA for Hadoop, 2.x series. We actually started with 0.20, I think. And then we keep upgrading our designs to one point series, two point series. And also some of you may find that in the beginner community there's some kind of funder distributions. Like Houghton Works, cloud error distributions. We also designed some plugin-based components so that you can integrate it with your HTTP or CDH distributions.  So we take the HBase as an example application framework. So we bring RDMA into it. And like for key value stores, these days memory cache D or like Redis, ROX, DB kind of things are also very popular. We bring RDMA into memory cache D, see what kind of benefits people can achieve from the RDMA protocol. So we have a large user base right now. We have like 225 organizations from 30 countries and more than 21,000 downloads from our project site. This solution can run with InfinityBand as well as Rocky. But if you only have v-cell, it can also run as well. This is like a super set of the default version. Okay, for Hadoop 2.x distribution, the latest version we support is Hadoop 2.7.3. Okay, this is almost the latest one. This day's 2.8 is coming. So we are working on merging to it. We will make a new release in the next several weeks maybe. So we have very good designs like RDMA-based HDFS, RDMA-based MapReduce, RDMA-based RPC kind of things. Okay, it can also run MapReduce directly on top of Luster or other parallel five systems without HDFS involvement. We can also run these workloads on top of burst buffer-based design. For example, in our group, we develop some burst buffer on top of memory cache so that you can run your workloads on top of burst buffer layer. Okay? So this is like a different modes we support in our Hadoop library. So for HDFS side, we can support purely like in memory mode. We are trying to help you get in memory speed for IO. Okay? But it may lose some foretolerance. But in some cases, if you want to have performance, then this may be a one-mode you can try. And then in heterogeneous mode like HHH, we call it Triple H. And then with Luster Integrated Mode, Triple HL. And then with burst buffer, Triple HL, BB. And then for MapReduce, we have two modes as well.  Another thing is for HPC clusters, we develop some kind of tools to integrate Hadoop with your scheduler, HPC cluster schedulers, like SNRN or PBS or Tokyo. Okay, for Spark. Similarly, for Spark, we have developed some designs inside it. I will give some deeper overview of what we've done in the next episode. And then this latest version 2.1.0 of Spark, we support that with RDMA. And then these packages available in our website, they're also available in supercomputers or cloud. For example, SDSC Commit. If you have XCAD account, you should be able to log in to Commit and run our packages. And also we have developed appliance which available in Committing Cloud. This is OpenStack based cloud supported by NSF. Okay. Now let's take a look at the best designs, what kind of challenges we've served through RDMA. So first of all in HTFS. Because HTFS is the major component widely used by a lot of big data midwills like Spark, Flink, or HPACE, everything. Then we take a look at what kind of communication requirements or IO requirements actually HTFS need. Okay. So then we do a lot of analysis. We see that the most communication IO intensive part is what? It's not read. Because read is a locality. Right? Actually it's right. Because when we do write, you need to go because of the fortress report, you have to do replication. When you do replication, your data has to be moved to different nodes. Okay. During that phase, you need to consume network. You need to use a lot of high speed IO devices as well. Right? So that's why we bring RDMA first into the HTFS write pass and also the replication pass. Okay. That's we call RDMA based HTFS write and the replication. Okay. Not only that, because if you just improve the communication part, the bottleneck may still exist on the IO pass. Right? Because you have to load that from disk and then send to network. If the bottleneck in the disk exists, even you have high-profile networks, this still doesn't help. You have to improve your IO pass as well. So that's why we bring some other designs to efficiently utilize heterogeneous story device like SSD, run disk, and VRUN kind of things. When also we do hybrid replication kind of technologies. We have a paper in CIS grid 2015. If you have interest, please feel take a look. That's for HTFS. And for MapReduce, earlier I give example of how MapReduce works. Right? Just record that. Where is complication? Where is complication? Where you need complication? Shuffle, right? You have some output from map face. You want to transfer this map output to the reduce tasks. Then how you transfer, how you move those data. You have to use network. That's also complication intensive phase. Okay? So that's why we first of all we design already may base shuffle. Not only that, similarly, if you need to get data every time from disk and then do the shuffle, it's still slow. So that's why we design some prefetching and caching of your map output. And then we do memory merge rather than on disk merge. Okay? So with all these kind of designs, we are trying to improve your application. We, you know, run in a much faster manner. And another goal is don't change your application. Everything we done is in the middle, in the library, so that your application can run transparently. That's the major goal. Now let's take a look at some of the performance, example performance numbers. So this is like a Apache Hadoop random writer Terrigin on top of if Infinity Band EDR 100 Gbps. We see that around thick 3x or 4x performance improvement. Next one is sort and Terrasort. Maximally, we can achieve like around 60% improvement. Okay. Now let's take a look another one next to take a look at Spark. In Spark, similarly, even though Spark is trying to bring your data processing in memory, but still when the wide dependency happens, you still need to bring your data from different nodes. That phase, we still call shuffle. We still time consuming, communication intensive and IO intensive. So what we bring is in default Spark, you have like NIO or native based components. We bring the already made based parking designs under in the Spark core. So with this, we are able to see around 80% improvement for RDD based operations, this Gruby and Soluby. This basic RDD operation. Very simple micro benchmark. And then for next one is graph benchmark, which page rank. So we run up to 1,536 cores, full subscription on 64 worker nodes on SD's comment. This is another, this is a supercomputer. We can achieve around 40% performance improvement. Okay. So that's like, just like a back benchmark or benchmark. So these days, people also trying to run deep learning on top of Spark. One of the example is Big deal, is developed at Intel. So basically they are running parameter server kind of architecture. Okay. They run their deep learning models on top of Spark. And then the data will get a shuffle through the back end of Spark. Okay. There are a lot of interesting features for Big deal. If you have interest, please feel free to go to this link. Take a look at their features and the user guide. We want to show some earlier numbers we observed. This is just for one EPO competition phase. We see that with RDMA, this VGG training model on top of C410 dataset. We are able to see like around full X performance improvement. That's very exciting for deep learning workloads. Just bring RDMA into your stack. Okay. So that's for native environment or bare metal environment. Now let's take a look how to run RDMA Hadoop on top of cloud. Lot of challenges here also, right? What kind of performance characteristics of your native, of your RDMA pass on top of SRV channels? What kind of locality of where designs you can bring? And how to detect the cloud topology and how to design some virtualization of where policies in Hadoop. And how to bring these things into the Hadoop stack. So this is the dimensions we actually can try to learn or try to design to explore the designs to utilize HPC cloud networking technologies. You have different network the kitchen for example, QDR, 4DG, DSTACE or 4DG, ROCKY, FDR, EDR. From this dimension you have like different protocols. You can run TCPIP, you can run IP over IP, you can run RC, UD or hybrid, whatever. And then you can run with SRV, you can run with a fair amount of environment. And then how to design your stack to consider all these kind of different generation of architectures and the protocols. So we just give you one example because RPC is being used for in many big middlewares, for example HBASE, right? So this is the default pass you can run, you can run default HBASE or RPC or top of TCPIP over UDP or TCP protocol. You can also run with IPOB with RC or UD. And then like I said earlier, we designed RDMA based protocol for big middlewares. We want to try that. Can this design take advantage of multi-channel or multi-protocols? For example, like RC, UD or hybrid, okay? So we designed some kind of protocols we can hybrid RC and UD protocol because RC can support RDMA but UD cannot. But UD can help you to do that reduce memory utilization because you only need one peer to complicated with one EP to communicate with all the peers. Now let's take a look at performance. If you take a look at this, the red one is the IB with RC. So we see that that's the best performance we can achieve. And then this one for HBASE. The maximum we see around 2.6X performance improvement, okay, with the best protocol selection. And for Hadoop similarly, for different components for HDFS, we designed block management to improve for tolerance. For yarn, we designed some container allocation policy to reduce network traffic, map reduce Hadoop components. For Hadoop common, we designed some topology detection modular to automatically detect your topology of your cluster. We integrate these designs into the RDMA Hadoop. If you want to take a look at some numbers, we see that for color burst and self-joining applications, maximally we can reduce the screen time around 55%. Okay, that's some kind of designs we provide. Now let's see how to do the fast provisioning. So like I said, open-start heat can help this phase. So this is the heat architecture. We want to get some physical node. And then we launch VMs. In the launch VMs, we need to handle a lot of things. For example, SRV channel, setup, network setting, image management, launch VMs, and the month global storage. These kind of requirements are there, okay? But with heat, we actually can design all these things in a template manner, right? We can write these things in a heat configuration file and the heat can take over all these kind of things like load VM config, allocate the ports, allocate the floating IP, generate a key, blah, blah, blah. And then it will develop the whole Hadoop stack and the Spark stack for you. This is just a quick demo on top of OpenStack. So this can, we first create a list and then with this one important thing is we need the infinite support. Infinite support here. Because we run with RDMA, right? And then this stack with heat. So we need to select what is the list, what is the rest of the key, and how many total physical nodes you need, how many total VMs you need, and then how many virtual CPUs for each VM. And yes, these kind of things.  And then this is the phase, get launched directly. And then this is the overview of the stack details. And then in output, actually, there's the important thing is that we were directly automatically assigned a floating IP on your master node so that you can access this cluster through this public IP. Wherever, whatever terminals or SSH, through SSH. So we have a lot of going plans on this project. We are trying to upgrade to latest version of Hadoop Spark. We are also trying to support streaming, do automatic tuning, Impala, Swift, and deep learning with that. With this, let me conclude this talk. So first of all, I'm trying to give an overview of what kind of challenges of accelerating big data processing with HPC and the cloud technologies. We present a lot of designs or opportunities to take advantage of our RDMA and SRV. I mean, it may be hard to get all this information in just the 40 minutes talk, but feel free to come to me and we can discuss it offline. And we have a lot of materials in the website as well, so please feel free to take a look. All the results looks promising. And the one important thing is that this kind of stack is very complicated. If you want to deploy it by yourself, it's very hard, but with open start heat, you're able to deploy it easily, especially we share this template on the website. You can easily use that and then deploy it. And then all these things, we are trying to enable big data and cloud computing community to take advantage of modern HPC technologies to carry out their analytics with high performance manner. So I have two more talks tomorrow at 4.30. I will introduce what we have done inside OpenStack Swift to bring RDMA into it. Second thing is that the day after tomorrow, we will introduce how to build efficient HPC clouds with MPI, OpenStack, over SRV and RDMA and also how to support migration. So I'll just acknowledge the sponsors. So we are seeking for more opportunities from you guys. And then this is the acknowledgement to the personnel from our group. Thank you a lot.


Resistors are color-coded with markings or bands that allow you to quickly identify resistance values and tolerance. Using a color chart table will allow you to determine the value of any common four-band resistor. Memorizing this color chart will enable you to become proficient at quickly decoding and using resistors. In a four-band resistor, the first two bands represent the digits or significant figures. The third band indicates the multiplier, and the fourth band indicates the tolerance. You read resistor bands beginning with the end that has the most bands. A space between the third and fourth bands also indicates the reading direction. The first band is red, so the first digit value is 2. The second band is violet, so digit 2 is 7. The third band is yellow, so we multiply the first two numbers by 10 to the fourth or 10,000. Thus the value of this resistor is 270 kilo ohms with a tolerance of plus or minus 5%. In this example, the first band is orange, so the first digit is 3. The second band is white, so digit 2 is 9. The third band is silver, so we multiply the first two numbers by 10 to the negative second power or 0.01. In this instance, we would take the 39 and move the decimal point two places to the left resulting in a value of 0.39 ohms. Thus the value of this resistor is 0.39 ohms with a tolerance of plus or minus 10%. Now let's determine what the bands would be on a 15 kilo ohm resistor. Since the first digit is 1, the first band would need to be brown. The second digit is 5, so the band color would need to be green. The resistor value is 15,000 ohms, so we need to add three zeroes to 15. Three zeroes is a thousand, so we need to have a multiplier of 10 to the third. Thus the third band would need to be orange. The last band would need to be silver to indicate that the resistor has a tolerance of plus or minus 10%.


Hey! Hey there, dude! SquirtedSlogan here with another reaction video. And today we're gonna be reacting to Seventeen on Crack. There's this channel that you guys have been telling me about called Lollikitty. And I decided to check him out or her out. I don't know who her it is. Um, but yeah. I saw that day I was like, scrolling through the videos and I just found a Seventeen Crack video. So I was like, why don't we do this? Because my learning, like, funny moments is always a great way to learn people, okay? It's just always a great way. And I've learned quite a few of the members. So I'm gonna see if I can, um, recall all of them that I know and all that stuff throughout this video. Because it has been a while since I have done a Seventeen video and I am sorry about that. But, uh, yeah! Other than that, let's get straight into this. I'm freaking excited. I hope you guys are too. And let's do this. Oh! Oh! Hey, guys! How are you? How are you? Oh! Fancy intro? Fancy intro? Yeah. Yeah. Yeah. Okay, that's all the members. I just published what he's doing then, but I, I'm not. I should probably be like, sitting next to him, but I'm not because I don't know why. Got that. Oh, I'm crack. Okay, a lot of kitty. Okay, Vernon, what are you doing? What are you doing? What are you doing? What are you doing? Is that Vernon and Joshua? I'm not, I was a little too short. Well, then, damn.  I will never mess with you. Do you mean Jacqueline? Oh! How long can you do? Ah! I can't remember the head. Oh, there's Seungkwan there, though. I see my boy, Woozi. My boy, Woozi. Seungkwan! Look at 7, Seungkwan is. Game freaking rigged. Okay, it's Goobz. Oh, that's Pil, a pie. Oh, where is he with pink here? Yo, that's cool. Damn! Oh, I hear that for the debut song, eh? Why would you hurt a fan? Come on, Vernon. Okay, I thought that would be helpful for learning the members, but it wasn't really helpful. I just laughed and it was a fun time. Okay, so I'm probably still going to do the rest of this series because that was pretty friggin' funny. Ooh, he's got English time series as well. Ooh, I'll check that series out after I do the 17 Crack series. But yeah, I actually thoroughly enjoyed this. This was a good way to know their personalities. I didn't really learn any members' names. I think I might have to still do some videos or just do it in my own time. Do you guys want me to do videos for learning the members? Because apparently they got the series going, so I'm pretty sure there's a series, one of their first ones, and it's been recommended for me to react to, and I will do that. I will do that if you guys want me to, but I can just learn the members through my own time as well. So just comment down below if you want me to learn them in my own time or learn them in video, so I can do that. Because I don't mind doing it. Like, 17 Crack videos, 17 learning members, 17 English time. I can do all that stuff for you guys if you want it because I really want to slip into it. But yeah, guys, this is going to be all for this video you guys did and enjoyed. And if you guys didn't, definitely talk to them to a pop by leaving a like and also comment down below if you want me to learn the members through my own time or do, like, continue learning members through videos. And also if you want me to do the English time after this series or at the same time reacting to the 17 Crack series because this is actually pretty freaking fun. And also, let me know if I got any members wrong. I'm pretty sure I got Joshua wrong because I was a bit iffy on that. I was like, is that Joshua? Is that not so? Please let me know if I did get Joshua right. That was, like, one of the first clips in this video that I reacted to. So please let me know by also commenting down below. And also, subscribe if you guys are new to the channel because there will be more 17 videos coming to you guys in the future, so stay tuned for that. And yeah, I hope you guys have a great day. And just keep on smiling. And adios, amigos.


As we all know, Stephen Curry is one of the most clutch players in the NBA, but this is a story about his clutchness at a very, very young age, and we're not even talking about high school here, we're not talking about college, we're not talking about when he was a rookie. This is when he was in 8th grade, and this is his coach, his 8th grade coach, recalling a story about Stephen Curry taking over a game. Now obviously, he's become widely recognized as one of the top players in the league, two-time MVP, a unanimous MVP, in fact the first unanimous MVP of all time, some disagree because of the fact that Jordan was never unanimous, and Jordan is seen as a better player than Curry, LeBron is not ever unanimous, so it's pretty crazy to think that Stephen Curry, a 6 foot 1 to 6 foot 3 point guard, was the first unanimous MVP, it's pretty crazy, but I mean his team did break the all-time record wins, 73 wins in a regular season, which is pretty crazy as well. So the amount that Stephen Curry has put into his game to make him one of the best NBA players in the NBA today is a lot, he put in so much work, but this story is way before he really knew he was making it to the NBA. In fact, Stephen Curry, if you've really followed his journey, he never knew that he was making it to the NBA, of course his dad played in the NBA, but a lot of schools didn't have faith in Stephen Curry, I mean he was undersized, he wasn't amazing, he was just a solid shooter, and he didn't really know if he was going to make the NBA, but now as we all know he's one of the best players in the NBA, and this story really shows the first glimpse of what he could become, he was in 8th grade, remember that. In August 2017, Stephen Curry's 8th grade basketball coach recalled an epic moment during a game where the Warriors star showed some flashes of his potential self at a very young age, he said, the Saints were down by 8 points with about a minute left in the championship game, remembering Stephen Curry obviously played for the Saints, it was a championship game, and they had an undefeated season on the line against Hillcrest Junior Public School, they had multiple guys who were 6 foot plus, which obviously in 8th grade is pretty tall, coach called a time out, huddled on the sidelines with his players, he says, guys I think we're going to lose, I'm out of ideas, I have nothing left to give you on how to beat these guys. Now first of all, number one, what kind of coach is that? He just told his players that they're probably going to lose. Come on coach, you've got to be better than that. Second of all, obviously you know it's time, I mean one minute left, this is Curry, this is clutch time alright, Curry then piped up, give me the ball. Coach goes alright, just give him the ball.  I've never seen anything like it, like he said, we ended up winning the game, it was a 13 point swing around and it was entirely because of him. Now I don't know about you, but the way that Curry's changed the NBA in today's landscape is pretty amazing, Curry seems to be able to change the game in the span of a minute to five minutes, the way he can shoot is amazing, it's incredible, the way that the Warriors play is obviously it reinvented the game of basketball, everyone pretty much nowadays runs the small ball, although it didn't originate from the Warriors, the Warriors really implemented that into their game and they were able to use it to be one of the greatest teams ever assembled. So for Steph and Curry, this was obviously the first sign of greatness for him, the chance to be clutch, something that every young player dreams of, but Steph and Curry isn't the only one that possesses this clutch gene, another player is Curry Irving, which if you guys want to see a Curry Irving young story, when he was clutch at a very young age, I can make a video on that, I know a story about Curry being clutch at a young age, but this story just makes it even more clear that Steph and Curry has always possessed the utmost confidence in his ability, which is why it makes him so fun to watch and it also helped him fuel to reach the point where he is today, a two-time MVP and obviously he's won two out of the last three NBA titles, Steph and Curry obviously is taking his game to another level, every year he seems to take another level, apart from maybe last year, ultimately this is an anecdote and it just shows you something that Steph and Curry has had for a long time, the ability to be clutch and it's not something that all players possess, anyway if you guys enjoyed this video and you want to see more videos just like this one, be sure to leave a like, if you're new around here, definitely hit that subscribe button, a lot more NBA content just like this, more stories, more what ifs and I really want to get back into the conspiracy videos, I made one about LeBron James and his brother and father, if you guys want to watch that video I'll leave a link to that in the description box down below, but the next one I want to do is about Otto Porter and Will Chamberlain and I know it may seem crazy but the whole conspiracy theory is it doesn't have to be real but we analyze and dissect why it could be a fact, even though that's obviously what we're going to do in the video, so if you guys want to see that, be sure to leave a like, subscribe if you're new and I'll catch you guys in my next video, I'm out, it's been your morning Smith, check out the new merchandise and I'll catch you guys in my next video, peace.