Welcome, we are going to go through a program that I put together. This is originally designed for actually use with young people that we're teaching more information to, so it's a pretty foundational force. I think there will be people here who will find this new information and people here that will find it old information. So answer me a question with a raise of hands, how many here has bred at least one litter of puppies? Okay, good. Good, good, good, good, good. How many has bred, say, five litters? Good, excellent. All right, how many has been doing it since you could walk? Since you could walk? Okay, excellent, breeding dogs. So this is really going to be a good refresher course and hopefully have some interesting information. My goal is to go through the slides, do the talky talky part, and then we can have a conversation, because I think that's how we all get our best information. All right, so basic concept, we're going to talk theory. Then if we have a little bit of time, we'll do some hands-on stuff and we'll get into some questions. Reading pedigrees is something that I think too many of us don't do as much of as we could, right? I know in the dog show world, a lot of people are busy breeding to ribbons, and I know enough folks in this organization that are breeding to scores. And I think it's important that we be able to get information, gather information, know about the dog's genetics matter, okay? So I don't have pedigree programs. They only run on IBM's. Macintosh is not designed for it, but I have friends in high places. They're really helpful. They're going to help you be able to see COI, right? So the coefficient of inbreeding. This has gotten to be sort of a hot button topic. So if anybody's ever read this book, Bob Wheelie's Snakefoot, he's all about inbreeding. He's not real worried about COI. I think there's a lot to be learned in this book. If y'all don't have it, I recommend it highly. But what COI, sort of today's concept of COI is that too high a COI can be correlated with an increase in health problems and a decrease in reproductive ability. In other words, your litter sizes go down, your puppies aren't as thrifty. So that is the current science. I, you can't fight science, but I think there's a lot of background and a lot of knowledge that we lose if we go too low with COI. Now we don't have a purebred dog, right? You can get too low on this. So I think there's a lot of balance in that part of what we want to talk about. These programs are handy because they highlight different things. So I love doing photopedigrees. For those of you that have the capability, it's a lot of fun. You can even pull out pictures, right? Pull pictures out of your files and lay them down in a pedigree system. Because then you really see what you're actually getting. Whether you want to see pictures of these dogs standing on point. Whether you want to see pictures of these dogs standing so you can see their structure, whatever you want to see. It's really helpful to be able to have those photos. So if you don't have, like I do, seven generations of your own dogs in these pedigrees, go find pictures. Go look at old magazines, right? Go look at your old breed magazines. There's places you can find some of these things online and make yourself a photopedigree even if you're just laying it out on the dining room table. Of course, if you do that, you should definitely clear the table before dinner set. Because I'm saying they get a little grouchy about that. It's one of my mom's old pedigrees. So this is the way a lot of us learned how to do pedigrees is writing them by hand. And she would write out a pedigree like that for every single one of the puppies in the litter. You really get that brain to hand connection when you write 10 pedigrees for five generations of that. And there's a lot to be said for that in terms of really knowing where those dogs are placed. So now we're going to get a little more in the nothing bolt. Inbreeding, linebreeding, and out crossing. And a lot of people will argue whether inbreeding and line breeding are actually different. It's the difference in inbreeding and linebreeding is in percentages. So how close are your related individuals? How far back are your individuals? Out crossing is when there are no individuals related. So let's look at some of those pedigrees. Inbreeding, the way I think of it. Father, daughter, mother, son, half brother, half sister. In 40 years of breeding dogs, I've done one half brother, half sister of breeding.  That's how long it took me to feel confident enough to do that much linebreeding. I did Uncle Nice and really love it. And I think that is the, if you will, safer way to do a lot of the same basic concept. So then when we talk about, so there's that letter that I just did.  Sure, well I hate trying to do this without a pointer.  And this was actually even a bit more than just the half brother, half sister. Because you'll notice that the tiger of the dam and the sire of the sire extra time and extra postage are litter mates. That's a really tight pedigree. It produced what I wanted it to produce. It told me what I needed to know. I've got good health. I've got great coats. I've got great minds. So I was taking with that pedigree 25 years worth of everything I know about my pedigree and putting it into that one breeding. But I think that's the responsible way to do in breeding. Because you are concentrating both the positive and the negative. All right? So you've got to know what the negative is before you get there. So breeding within the family of dogs. So you've got dogs that are similar, that appear, that they're usually maybe three generations back. I did a lot of line breeding on a wire hair pointer named Cascade Rogue. And he would just keep appearing and keep appearing and keep appearing. And I did that intentionally. And it's called putting the weight of the pedigree at the back. So I wanted to pull forward those characteristics that he produced. He was the top producing sire of field trial, title dogs, show champions, and hunt test. All three, he was in the top 10. So that's a pretty impressive thing and something I wanted to continue carrying forward in my pedigrees. This will do the same basic thing as inbreeding. It just takes a little longer. But in my opinion, it's also a little bit safer for me in terms of being able to keep track of where your health issues are coming from, temperament issues, any of that kind of stuff. So this is that type of pedigree. This is the pedigree that, again, produced very, very well. The dog that it produced was the number one show dog in the country. It did what I wanted it to do. He also has a hunting title.  So this is just carrying some of those dogs forward, but not right up on top of each other. That's this to me is a really, really safe type of pedigree when we're trying to fix traits and not bring forward some deleterious parts of the gene pool. So up cross. Even Bob Wheelie will tell you, got to do it sometimes. You got to bring in a little bit of fresh blood. And I think one of the things that we lose track of with this low COI concept is if you don't have inbred and linebred lines multiple, you are doing a disservice. Because when I take this inbred line, linebred line, and this inbred line, linebred line, and cross them, it's effectively an outcross. But if I don't have a tightly bred solid line to go to, I've got nothing but mishmash, then I'm not able to reliably bring something forward. What does this mishmash give me? Up guess. Some random whatever thing might pull down, right? If I've got a solid bred line of dogs that I can effectively outcross to, then I'm in better shape. So this is an example of that type of pedigree. This is as outcrossed as a dog can possibly get.  There is no similar dog in here and to the founders. And we could not find a similar dog. So the sire, my dog, slightly linebred, very loosely linebred. The dam, there's a couple dogs that turn up and what is that, the fifth generation. This is a pure wash is what I think of it. I have washed the gene pool. I have deleted all the crazies. I like to do this every couple, three generations to just make sure that I'm keeping reproductive health, all the temperament pieces. I know that I'm going to go a step back when I do it. My mother used to swear that she'd go out to get one thing. She'd get 10 things she didn't want. And that's a fact. And it happens to all of us. But the important part of that then is selection and selecting what you did the breeding for. If you did that breeding to get, I don't know, a better head and you keep the bucket head that looks just like everything else you've always had, you've wasted the litter. All right, health testing. Health testing matters. Why would I test the? OK, we want healthy dogs. And there are no guarantees. I have a litter that I have four OFA excellence, four OFA goods, one that's sort of like a eh, and one that is so dysplastic we had to have her hips replaced. Welcome to it. And that's seven generations of line breeding and testing. But that doesn't mean you don't do the testing. And there's a lot of good information available to us today, Canine Health Information Center. Anyone who's not familiar, your parent club has put together a list of what are the required tests for each breed based on a health survey within your individual breeds. So each of those tests is create the goals or put together by the parent club. It's not generic. It's specific to your breed. So in Warwick Hooners, it's hips, elbows, thyroid. Eyes and heart. And so testing your dog in each of those areas and releasing the results. The releasing the results is the part that matters. So the whole point of the exercise is knowledge, sharing of knowledge. If your dog has bad hips, OK, it has bad hips. Tell people it has bad hips. Then they can make appropriate breeding decisions. You don't have to throw that necessarily out with the bathwater.  That's the entire purpose of the CHIC program. Just because a dog has a CHIC number does not mean it passed all the tests. Go look it up. Just because it says CHIC number, 180 billion. Great. Oh, look, it failed all of those tests. OK, that's a thing to know, too. But it's the sharing of information that is what makes the CHIC program so incredibly important. The next one is DNA. DNA wasn't a thing when I started in this world in the 80s with my parents in clumber spaniels and field trial labs and wirehairs. There was no such thing. The only thing we had was parentage, and that didn't come until well into the 90s and early 2000s. Today we have really specific DNA that can test, for example, furnishings, big F, little S. It can test for various eye diseases. It can test for a lot of things. What it cannot give you is any more guarantee than any of what we think of as the physical tests, right? The hips, the elbows, the heart that we are physically tested. DNA isn't going to give you any more guarantee of that than anything else. The only thing it will tell you is that these genes are present, and you still have to make decisions with that. But it does allow us to make decisions. If you have a disease in your breed that if you breed a carrier to a clear, then you get carriers and clears. You don't get affected. You can do that, and you haven't lost all the genetic material that goes with a dog that's a carrier that otherwise you would not be able to breed. So DNA has a really important place and should be part of your project as you're breeding these dogs, to know what you can and cannot do and where you can go with it. This is a vertical pedigree. How many of you have ever looked at this on OFA? Couple? All right. This is conceivably the coolest free breeding tool you will ever encounter. Did I mention it's free? It's phenomenal. If you're not using it, you really need to because check what you can do. This happens to be my stuff done. It happens to be hips. You can do this on any of the tests that they do. All right? And it's gonna tell you all the dogs. There's big. He had nine siblings. Five of his siblings had good hips. Two of them had excellent hips. When I did this, his two offspring had not been tested yet. His sire had two siblings. One was excellent. Now one, so what happened to the other one? Oh, probably they didn't report it because it wasn't good thing to know. We've got 18 offspring. 10 good, five excellent. Wait, what happened to the other three? Thing to know, right? You can do that all the way back through the pedigree. And what you're looking for when you're breeding for things that are what we consider polygenetic, right? It's not a simple recessive. There's a million things that go into hip dysplasia, including environment, right? But you can, with this type of pedigree, this vertical pedigree, you can understand so much more because I would rather breed to a dog that is itself, say, fair, but its siblings, its cousins, its nephews and uncles were good and excellent than I would to a dog who itself is excellent and everything around it is fair. Does that make sense? The depth of the pedigree is what is carried forward, not just the individual dog. This is invaluable and it is free and it's easy. No excuse not to be using this particular system. Okay, science-y stuff.  Boys and girls. This is another book that I'm gonna recommend to you guys. I'm gonna come up here so everybody can see it. I know it has show-dog stuff on the cover. Do not let that freak you out. This is the single most important book on dog breeding. I believe that exists. There's a lot of stuff in here about show-dog stuff, but there's more stuff about dog breeding that is applicable to everybody. And I'm gonna pull from some of this in this particular section of this program. This is the part that I added for you guys because it was like 102 instead of 101, right? Okay, x, y and x, x. This was when I read this book. So I was a grown-up. I was having my first litter of wire hairs. I was first time breeding something other than with my parents when I read this book. And it became my Bible. I had to buy a new copy because it was highlighted and tagged everywhere. But it was so revelatory to me thinking about what she was talking about, the tail female line and the tail male line. Males are x, y in their chromosome. Females are x, x, okay? The male can only get their x chromosome from their dam. It's the only place they can get it. And the y is what makes them male. Females are getting an x chromosome from their dam and also from their sire's dam. Do the math in your head, right? Math isn't my forte, but I'm saying it. The tail male line coming down from the sire, that's where your y chromosome is coming from. Tail female line, the x chromosome coming up from the bottom, okay? So this is a really important slide and I'm not sure that this is gonna come up but if you guys wanna look at this book later, I can let you take a look at it. Look at that x chromosome. Look at what that's doing. So this becomes incredibly important. That x and that x and they're carrying forward. The top tail male line, all that's coming down is there's the y and the y, but here you're getting an x and an x and an x and you're carrying those chromosomes from the dam line. So again, if I'm looking for a stud dog, somebody I know had mentioned a question about whether they should breed their stud dog, so we'll get the Q and A in a minute, but if I'm looking for a stud dog for my bitch, I want to find a dog that is out of a line of phenomenal bitches, because that's what I'm gonna get from. Does that make sense? It's not so much the sire as the sire's mother. Okay, the only x chromosome that can be passed by a sire is the one he got from his dam. This is what I'm saying. Pategris with excellent breed bitches, those bitches that produce and produce and produce the Adels of the world, the tailors of the world, they come from sires that come from strong dams. Okay? All right, how are we doing on time here? All right, we got time. So hands on. And there's a reproductive vet that's gonna do a lot of more of this stuff, so I'm gonna skim it and leave a lot of the rest of it to him. Heat cycle, we all know, right, that we're not breeding on that first heat cycle because we want to wait to get their health testing done. For one, those hips can't be done until they're two years old. Wait till the dog is strong enough, healthy enough to reproduce and raise your puppies correctly. A lot of times that sexual maturity is gonna be six months, but I've had plenty of bitches that didn't come in season till they were nine or 12 months, not the end of the world, just pay attention, be aware. Twice a year, unless you have a synges, then it's once a year, I'm pretty sure we're safe here, so say it. Generally your full heat cycle is gonna take three weeks, some of them are longer, some of them last what seems like four effing ever if you have boy dogs. Bitches carry their puppies for nine weeks. They say 60 days or whatever, it's nine weeks, count nine weeks. If you are not using ovulation timing, you're crazy. Where's my repro vet that's gonna say the same thing? Okay, you're crazy. Because if you just throw Annie and Rex out in a pen and they do the wild thing, they don't welp from when they did the wild thing. They welp from when they bitch ovulated, which could have been two days before or six days after which I've had happen. Trust me, that was terrifying pre ovulation timing. If you have to have a C-section, you don't know. And you're gonna have to do reverse progesterone timing. Is she low enough? Is she too high? If you do ovulation timing, pull progesterone, get blood, have the vet test it, you will know when that bitch ovulates and she will welp pretty much to the minute within 12 hours more or less from that day in nine weeks. Makes your life so much easier. Why should you all be doing it the way I did it when I was 18? Catch up with times. Ultrasound, again, you don't have to. Usually the next week, I know she's bred or she's not bred, but an ultrasound tells me if there's something that looks a little weak, something that maybe they're all in one horn and not the other horn. I like to have an ultrasound. It gives me more information. There is an entire program that I can do on proper nutrition, proper supplements, exercise, all the things that we need to be doing for our bitches to make sure that they are welping as healthy as they can. Mildred Revelle got rest or soul was one of my early mentors in wire hairs.  God love her. We don't have to do that today. We have other options. And it makes a difference. Most of our bitches are gonna be easy, but stay close, pay attention. See if they need help. C-section may save your life.  It will definitely save puppies. I've had welpings that were done in eight hours and I've had welpings that took 24 hours. Be prepared. Lots of coffee and probably some wine. All right, puppy development. Any of you who are not familiar with some of the really great programs that are available these days came undone. There's some amazing opportunities to make our puppies develop the best they possibly can. Early neurological stimulation, scent introduction, all of these things are available and we know more. There is more information, there's more knowledge. So, neonatal period, from when they're first born, their eyes and their ears are closed, right? They can't hear anything, they can't see anything. They can smell a little bit and they are basically heat sensing worms. They cannot control their body temperature until about 10 days to two weeks. They are gonna go to or from the heat source and the food source. That's all they're gonna do. We start early neurological stimulation at three days. Okay, so what we're doing is that three days that puppy's getting picked up, tell ups up right, it's head up in the air, five seconds, one, two, three, four, five. Upside down, head down. One, two, three, four, five. On its back, one, two, three, four, five. Set on a cold surface, one, two, three, four, five. Tiny stressors, tiny stressors that start when these puppies are three days old that make them better able to cope with bigger stresses down the line. It is absolutely uncanny, the difference. I've been doing it this way for years because I had early mentors that did army pain ups.  Okay, puppies not potatoes. Right, the best part. This is the best part of puppies. I don't like the beginning and I don't like the end. But the puppies not potatoes, best. They're cute, they're little, they don't have any teeth, they can't draw blood. It's amazing. Their eyes and their ears are starting open, right? They started to play, you know, weevils wobble and they don't fall down, so cute. About three weeks, the best. Three to five after that, done. Sent and sound introduction, right? So, and it does, it can be a bird wing, it can be a red fur, it can be clove, it can be anything. We're just letting them smell a new scent. They're developing the concept of using their nose. Sounds, my puppies all have YouTube videos of duck hunts that play in the welping box from the time they're three weeks old, the whole time. Clang the pans from the time they're three weeks old. Put their food bowls in different places so they have to do a maze to get to them. Early neurological development of our puppies, what we can impact from zero to eight weeks is incredible. And it makes well-developed, well-socialized, balanced, sane dogs in the end. Now they become explorers and they're really fun and that's where we start doing more of the tests and they have to, they want out of the box, fine, you can get out of the box, you have to go over the slide and through the tunnel and you have to do all the stuff. Okay, that's that four to five week time. Oh look, we even get audio, check it out. I didn't know that was a video, check it out. What? Okay, yes, we can do it. We can go down the slide. Boom, boom, boom, boom, boom, boom, boom, boom, boom, boom, boom. I forgot this was video. Here we go, here we go, boom, boom, boom, boom, boom, boom. Problem solving. So great, great, you're teaching problem solving. That's exactly what they're learning, right? And I'm not doing any of it, that's all them. That's the best part of it, okay? Okay, into the wild blue yonder. So when they start going to their new homes, I know that everybody read that thing where they said that you're supposed to send them home at 49 days. Guess what kids, there's a huge freaking fear period that happens in that seven to eight week time frame. Keep them at home, wear their safe with their litter mates, learning from their litter mates, learning from the other pets in the home, the other dogs, the mom, whatever it is. Send them out at eight weeks, they're past the fear period. Life is so much better, promise. Okay, here you go, more video. Wear your puppies, I mean, what could be better? Yeah, jump. And that's a good venture box. So you see that PVC pipe, it's got things hanging off it and they play with it, you can put tinged hands and banging stuff and all kinds of cool things. All right? And here's the resource shelf. I'm gonna leave this up while we do Q&A. These two books are on it. Anybody who wants to come up later and kind of look at these books, anything like that. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning. Morning.


So yeah, we're here to talk about Django in the real world, which is sort of the mostly issues about scale and performance using within your Django app. Before we get started, we'll have the panel introduce themselves. I'm Jacob Birch, I'm an engineer at RevSys. Hello, I'll take it out. I was sadly don't work with Django anymore, but I was an engineer at Whiskey Media that later became Berman Braun, so I have experience with running larger content websites. I am Frank Wiles, I'm the president of Revolution Systems, and we help companies with scalability and performance problems around Django. Peter Baumgartner, founder at Lincoln Loop, both build large scale Django projects for clients and also help them. I'm Andrew Bilvin. I'm a senior software engineer at Eventbrite, and we sort of have a big, like, transactional role in content. So before we get started, I'll just sort of lay out the format of this. We're going to try to do 15 to 25 minutes of me asking these guys a bunch of questions, really common questions that come up, and we're hoping to have a longer 15 to 20 minute Q&A session for you guys. I ask any questions you want of these guys. I want to start. Problems of scalability and performance are often sort of tongue-in-cheek labeled as happy problems. If you're having a lot of data or you have a lot of customers and you have a lot of bandwidth, a lot of traffic. These are usually good problems to have. Because of this, engineers and data architects and software architects will often prematurely optimize, even worse worry about premature optimization. And so what advice would you get people before they even run Start Project? What should they actually spend time on and make sure they get right the first time? And what doesn't matter until they actually have the happy problems? So yeah. Peter, you can start. Well, I would say early on you definitely want to optimize for developer productivity. You know, your goal is to build features and get this thing out in the wild as soon as possible. The things you want to avoid are making technology decisions that are going to shoot you in the foot later on.  I would say probably the biggest thing is to stick to the kind of known tried and true solutions. Don't reinvent the wheel and keep in mind you can scale with bigger boxes for a pretty long time until your scalability problems become code problems. So, yeah, you know, you stuff like Postgres and, you know, a good whiskey server and edginax or varnish. These things will get you really far. So I would say don't, don't sweat it too soon and don't use, you know, don't pull in some crazy technology just because you think you're going to need it. And I also add to that, I 100% agree, and I would add to that getting into habit of monitoring systems and looking into how things go. Once you move into production, you should always have record how things were, how things are now and where do you spend most of the time or what, what component is giving you the most problem. Even if you start with absolutely standard stuff, you should have this in place so you can later identify what's the problem and you'll never have to sort of guess and assume that this will help you or that that's a problem and that's the component that you need to write. And sort of feeding into that as well. Like I've seen a lot of code that was written to you very clever and then six months, let's start up six months online, the people or the sort of the knowledge of that has moved on and you go back like this is suddenly a massive technical debt. So like I would heavily encourage simple solutions with well known problems and well known technology because if you want to bring in people or bring in sort of external contractors, you want them to know what's going on as fast as possible by giving them this strange aesthetic environment with special new modules and a new database type you made yourself. You're taking yourself your own hole at that point. So everything they've said is absolutely true and you should absolutely do those things, but I think that it's kind of a natural key inclination to want to figure out what's the fastest way to do this. So I often will think about what happens when, right? Is there a clean, easy way to shard this data when we get there? Let's game that out. Let's make sure we don't write ourselves into a corner so that it makes that impossible 12 months down the road or you know what, if I denormalize this way, I will be able, you know, I know my access patterns are going to be like this and if I denormalize this and I use Redis, then I've got a whole bunch more performance. I don't actually go write that code. I just kind of whiteboard and game out what would I do when I get there? And so that satisfies the geek in me that wants to know what we would do and then we also kind of have a plan for when we get there, but we don't set up, you know, technological roadblocks that make everything slow for the early development. So I want to talk about the other side of things. When you have a site or an app that you, you did those things, you set it right and now it's against the wall. I hit the fan and it got slash dotted, it got fireball then all of a sudden things are going well. But before we do that, I was talking to Hansa yesterday and we want to make sure we sort of clarified a key vocab issue that comes up a lot when you start talking to people about performance or scalability and that's what is performance and what is scalability. They're often interchanged with, they often get using conversations with my website is slow, how do I make it not slow? Or I have a billion rows of data and I can't fit it anymore. So Hansa, since we talked about it, do you want to address that first? Yeah, so performance is how fast can how fast can you serve your content and that's very important for user experience and for general like operation side. And it helps the scalability, but it's not the same thing. Scalability is the question, will I be able to serve 10 times, 100 times, 1,000 times the amount of transactions, people or content based on my current stack. So that's the scale. Will it scale to serve more? And it doesn't necessarily have to be the same as performance. You can have systems that are super fast but don't scale at all and you can have systems that are fairly slow but will scale infinitely. For example, if you chose to use S3 as your database, it will scale almost indefinitely, but it will never be really fast. So anything to add to that? I think it's also sort of a difference in the approach. So certainly a Novemberite performance for us is so like we get a 5, 7, 10 cent speed gain if we're lucky out of the main rendering flow and that buys us a few months of headway. But the real sort of future planning comes from scalability, like we need to plan to serve 10, 100x people. Like a 10% speed increase is great, but it's only a short-term solution. Like you can't get by growing forever on just a series of small increases. You have to be able to have that big switch. So we did a thing with Django's regular expression URLs that gained us 5, 10%, which is fine, but then the sort of resources we gained have gone in like two months from that because we grow at that speed. So it's important, I think, to sort of see them as different kind of things. Sometimes you need performance gains, sometimes you don't. So yeah, let's go back to websites that actually need some of the sort of early gains of they've either got really popular or all of a sudden they have a lot of customer data that they need to store right away and all they're observing is we have this co-op and now things are slow. Now the website is crashing. What do we do? What are, where should people look first when this happens and what kind of questions should they be asking themselves and where should they look to fix their problems? So as I said earlier, into their monitoring, they should know they should have been monitoring all along and seeing it get to that place so they will know which part is the problem. No, this is Django in the real world, so let's say that isn't true. Yeah, so in that case, experiment and try to identify the piece that's giving you trouble, replace that and the important part is if you replace something, for example, you, in the real world, we found that we have a problem when Google hits our site and they tried to paginate to the 100,000 page. Literally had 100,000 pages and it was getting postgres obviously because it was sorted by three different ways, it was a huge dataset. So we replaced that with pagination with the help of Redis, so we would use Redis to paginate and then just use postgres to retrieve the rows. And then we went and so where else can we use this pattern to alleviate the pain that we have? So once we fixed one instance, we'd say, oh, now we have a different tool. What other uses for this tool we also have where it might help us? So this is also always the second step that not many people actually do. Yeah, I would say if you don't have good data, just going in and looking at the load on your servers. Is your database server overheating? Is your app server overheating? Figuring out where the hotspot is, just on the big scale, is it? Is it my database, is it my application? And then attacking it from that angle. If you can scale up vertically, that's a quick, easy win, throw some money at the problem, throw some hardware at it. Otherwise, sometimes really kind of quick and dirty caching solutions like database query cache, if your database is getting hammered, there's stuff like, let's see, we use Johnny Cache, Cache Machine, Cache Ops, Django Cache Ops, there's a few out there that will just, a few lines of code that can take up a ton of pressure from your database.  We were just talking about this earlier. It doesn't need to be for hours, it could be for five minutes. So far we've talked about sort of the ecosystem around the Django app. We've heard Redis mentioned, varnish mentioned, Memcache mentioned, is there anything missing in Django up to Django 1.7 that you feel should be in core to help ease growth? It's sort of always been Django's mandate to be very easy to get started and possible to scale out. Do you feel there's anywhere in Django that is either not in core and needs to be sort of smoothed out along that way? So there's a couple of things I haven't had my eye on for a while, so I know in cons as well that the key abstraction needs one of cons is sort of ongoing things. I'd also love some kind of message plus abstraction because in particular of Embroy as we're putting things separate services some kind of way, like if we had had that in the first place and said that these things, like the salary is great for sort of moving tasks off but it's not enough like cache and validation and stuff, so like I would love to see some kind of decent way of sending messages to multiple targets in Django with like a, we have made new events, we can develop new pages, we have solar tickets, we can develop accounts and stuff, like that to me is almost the missing piece at least for the thing we're facing now. I'm not sure we'd have a small site but perhaps it plays into like, you know, like live data binding like maybe, you seem to think Meteor does right, like perhaps we can have something where like, you know, we can have live data from this kind of system. It's a theory but I'd like to see something like that. I think there's some improvements that could be made to the cache framework in general. That's a piece that we seem to override a lot. One thing like on a high traffic site if you're using the cache framework quite a bit, you tend to see these spikes as your cache invalidates, spikes on your application and then, you know, everything gets cached and it goes back down and you get into this kind of wave, so one thing we do on ourselves doing is just adding like jitter into the cache timeout so, you know, cache timeout varies by 10% and you don't have all your content invalidating at the same time. There's a couple other things I know the trend is to try and take things out of core and put them out but I think that's something, a little more instrumentation in the core, so things like if run server as part of, you know, the logs showed you how many queries were run, something that Django Debo toolbar does great but something that was built into the system, we could have a little bit better probably testing, unit testing tools around some of those things. I know I end up writing like a, you know, certain number queries is less than this amount, like I don't need to have it know that it's exactly 12, if I wasn't in one six, yeah. There's a certain number queries, like that it's exactly 12 but I just want to say, hey, you know what, I only want to have this fail if it jumps over 50, something like that. We could get a little bit better around those. I'd just like to say that a lot of the things that have been said here actually don't need to be in Django, for example, what Peter said with the heading jitter, it's something that you don't have to worry about at the beginning and once you see this behavior, you can just grab an off the shelf cashback and from Github, from PyPI and just plug it in and it's a drop in replacement. It's also something that you don't, for example, use in development or in your staging environment. So those are the ways how you can progress. You start with a naive panel on Django and then you start replacing components, for example, for session storage or for the caching. We also had our own cashback end, which actually does the thundering herd protection that it will randomly not return the cash value once so it will get regenerated in the background instead of just having potentially multiple threads trying to do the same work and so on and so forth. We also expose a lot more because we use Redis as our cash so we expose a lot more functionality there instead of just the increment that the cashback end has, we do more and that's something that you can introduce later. So it's tied to the previous questions, like you don't have to worry about this in the beginning but know that these are the places that give you a lot of potential to do better. Yeah, I think instrumentation in general is something like even production instrumentation. I know you guys at Lanyard are using some kind of like backwards methods to get into, how many queries did this request fire off and then I wanna store that data or I wanna send it to StatsD or something like that so I can track that performance over time. It would be nice to have some better hooks into that information in production. Yeah, so the thing, I think I'll talk about Tiki Bar, I don't know, a member has a little Tiki Bar which is a similar use quite well, like we track the queries you run, that kind of stuff. There is definitely a lack of hooks in Django to have a easy third-party drop-in for interpretation. One of the things that now Migrations is much more done. I'd like to look at it as having those hooks in there so you can say like, okay, I do want to see every query that comes through in this list or I do want to like wrap this in a timer and that kind of stuff. I'd like to know how long my URLs always takes occasionally or how long my database calls take, how long my cache calls take. So if we can have some easy solution but that doesn't increase the overhead which is the key problem because Django gets unfortunately a little bit slower release then that would be a good thing to look at. So this will be the last question before we open it up to a floor. Four years ago, actually, not in this one, I was on the other side of the river but I moderated the panel on those SQL solutions at DjangoCon and it was such a popular topic that it was a plenary session, it was everybody. If four years since then of wonderful no SQL progress, it barely warrants a mention in this talk. Why do you think that is? Was the hype real? Yeah, I'll open it from there. First of all, the term no SQL is objectionable to me. Thank you. There was especially a bad time of prevalence of things like MongoDB is by far and away the most prevalent thing at that point in history. I think what's happened since then is that people have gone through that process, have seen that what they're exchanging, what they're giving up an exchange for that kind of document storage is some things that you kind of rely on later on when you're scaling, like things like indexing and easy changes and consistent data formats. And also at some point it's kind of become more assured Postgres now has pretty much first class support for schema of the stuff like just have JSON fields, they have indexes, it's I believe in the next release faster than Mongo is on most common queries. So I think it's kind of a combination of that. And then also things like Redis and Cassandra and React just came in all parts of the web infrastructure. Like the stuff that proved itself just became almost assumed. Like I still see talks about that stuff at conferences with people like well, obviously we use Redis and we use Postgres and we use Elastic Social Server because those are the three very complimentary things that like they can't do each other's jobs. You can't, you know, you could write a search engine in Redis if you wanted to, that's crazy to me. So I think that's kind of like the, we've settled down on those on the sort of more decided set and it's a bit of work. Yeah, I think the, you know, the talk at the time was, you know, how are we gonna get the admin to work on MongoDB or Redis? And yeah, I think we've now learned that you don't, there's no need to do that. You don't need to use these as your primary data store. For most people, most scenarios, relational database system is what you want to use for your primary data store, but there's all sorts of peripheral needs where those types of databases come in really, really handy like search and sorting and the kind of stuff that relational databases don't do. And also like if you use something else and relational data store, if you don't want to treat it as a relational data store, so there is no reason to pretend to hide it behind the same API to use the Django query set to query elastic search or Redis that in that case, like the different data store gives you nothing because you cannot use its entire power. You're limited to what an SQL database could do. So it doesn't make much sense. And people have realized like the ultimate promise of the no SQL movement, sorry, was like choose the right tool for the job. So if you have a search problem, use a search engine. If you just want something quick and easy and very easily updatable, use Redis. If you want something persistent and reliable, use Postgres. And like you can mix and match those. Just one, one item to the admin conversation. One of these years GSOP projects has been about exposing non-muzzle things to the admin. So, for example, there has been, I think it was Russ, a student who was doing, like they had Gmail backed onto the admin. So like some progress has been made in that kind of area separate from the whole sort of no SQL movement as a whole thing, but it's a different thing. The admin is a whole lot of topic and a whole lot of pattern, I think. All right, so we'll open in the forward of questions. We've got about a little over 20 minutes for them. So any questions you have for these guys, please come up, the microphone is on my right, your left. Oh, we have both mics, I'm sorry, I'm totally wrong. Either side works. Hey gentlemen, thanks for the awesome panel. I'm wondering, I think without exception we heard about elements of the app stack and their implications and performance and scalability. I'm kind of inclined to ask the same start project question that started this panel, but for the deployment tooling. Is it better, do you think, to use a company starting today, a small project starting today? Do they do like Jenkins from day one and Ansible and Docker from day one? Do you use whatever is hot and new the day that you start and what are the risks of that becoming a tradition and so on? So I think this feeds into my one of my first responses is that you should use whatever is common and isn't gonna get it. At some level, these are all deployment tools, they all have some level of common as like, I personally prefer Docker, that's more personal preference, like I designed the things in a little bit while ago, but I think whatever your team, whatever gets in your way the least is fine, because like deployment generally you can change later on, it's not sort of a fixed constant, like you can change points to some, usually that downtime is sort of ancillary to your main project. So I would say whatever you feel most comfortable with as a small technical team, I would go with that. Obviously it's doing things like taking two batch scripts, he's a real tool, but like between Ansible and Puppet and Chef and Docker and Jenkins. I'm inclined to fire back that Ansible playbooks and Jenkins config are fairly substantial bits of logic, I'm not sure that they're, I don't say they're not, but at some point you're saving time on those in the first few deploys and then everything after that is always payback. So I think don't have the gambler's fallacy, don't think because you've invested so much effort into it you can't change, like a deployment tool will save you time pretty much from day two or three, because like it's not only how fast deployments are, but it's the confidence in deploying, it's the speed of way, it's about you can just go hit a button and just sort of go and get some team, like this is fine, like I'm not sort of stressed and typing commands and like accidentally removing files. So like it's more than just speed and time investment, I think. Thanks so much, you mentioned monitoring several times and I'm wondering what sort of monitoring you love and a particular question also about monitoring is if you recommend keeping things like the Postgres logging on in production or not. You know, getting started, New Relic is pretty fantastic. It's only about 20 bucks later. But I mean honestly like for the amount of effort it takes to get there, that's I think for people starting out that's what you should do. At some point there's information you're gonna want that New Relic can't provide and there's other tools to do that, but that's not a trivial undertaking to get a kind of a full-blown monitoring system. Like MUNIN or something like that? Yeah, yeah MUNIN, there's Kibana and Elasticsearch, there's Grafana and Graphite and there's a million tools out there. I think there's a couple of different things.  Which traffic am I getting? What are the response times and all that and that's more kind of Graphite and Graphana tools there. Yeah, I think that it depends on the size of your company and whether or not you have ops staff, exactly what you picked. If you have dedicated ops people, then they're gonna have decent ideas about what they'd like to use and you just need to kind of tell them what you'd like to be able to see or what things that you think are important. If you don't use a service, there's hosted Graphite, there's Keen.io, there's all sorts of places that you can push this data and all it is is a little bit of setup config and a hundred bucks a month or something to your organization to get these services up and running and it gets you started. I think it took me more than a full day to get a fully working Graphite setup following tutorials online and I'd like to kind of think that I could set up a Django app pretty quickly but it took me like a whole day. So it's easy to get into a time suck setting these things up and then abandoning them and go, you know, we'll do that later when we really need this, we'll set it up later. Just use a service or something and get the data at some point somewhere that you can look at it. What do you think the Postgres logging, like I know there's a lot of great Postgres analyzers out there or maybe they're not, I was wondering. I think it's fine to do. Just don't log it to the same disks that the box is using for data in indexes. So use syslog, ship it off to another box and then like run PG Badger over it or shove them into Kibana so that you can look at specific queries and patterns and things. But yeah, the biggest thing is just don't have the, don't have the Postgres logs going to the same disks that your data's on. One tip with Postgres logs, I wanna just sort of bring up is that at landing element, right, we insert the URL of the current page as a comment into the SQL that will be run. So even in the logs, you can see where that SQL query came from. So our slow query logs says, well, these took 30 seconds, but they're from this URL. So we can exactly pinpoint where this has come from, which is a good sort of middle set that someone is missing in standard query logs. I think full logging is good for, if you need security or you have a breach or something and you wanna be able to go back and say, what exactly ran? But a quick thing you can do if you're on a recent version of Postgres is enable PG Stat statements, which is basically like a running slow query log. You can do all sorts of stuff and it's really awesome. So if what you're after is, what queries am I running the most? How slow are they? What's taking the most time? PG Stat statements. I'm sorry, I need to start with the disclaimer. I actually worked for Elasticsearch, which is currently the weapon of choice for storing centralized logs. So I'm gonna advocate really heavily for centralized. Now, the reason why I advocate for centralized logs is those information are great, but you need to take them into context. So you need to know like, so I've had this heightened load on the database. Did it also mean that I had more load? If then, it's okay. But if I had no more queries, no more HTTP requests on my app servers, that means that something is wrong and you need to sort of be able to correlate this. And that's where centralized monitoring and logging and everything can give you much more than each individual thing analyzed, even if that would be in more detail. Sort of to have this overview and to be able to identify pattern. So as Frank said, use a service, throw all the logs somewhere, visualize them. And over time, you will learn what was the most useful. So if you then grow big enough, congratulations, and you can build it yourself with just the most useful thing. And then you can start adding your own information. For example, with logs, it's great to index additional metadata. So structured logging, if you log anything, add all the information is there, in there. It was this request by an authenticated user or not. When, where did the user come from? And all this stuff that will give you more information. And even if you just store it on disk, so you can back load it later or you will do it only if you run into problems. Like even then to have this data, it's invaluable to be able to identify where the bottleneck is or where the quickest win is. I think one mistake to real quick on logs that people make is they worry about how long they're gonna keep them in a searchable state way too much. I mean, I need to refer to logs multiple times a day with different clients. I can't remember the last time that I needed more than four days ago. The only reason I needed three days was because the issue happened after five o'clock on Friday and I'm just seeing it on Monday. And the reason that I needed for four days is sometimes I don't get to that email until Tuesday. But like I've never even needed it a whole week. And so people worry about storing the last 90, 180 days.  And sure, also that they'd be able to load it in if you need to get to it, but you probably really only need to actually have indexed the last seven days of data in most cases. That's awesome. Can I ask one quick, what was your name by the way? Yeah, we have a problem. What was your name? Sorry. So that again? So what was your name, brother? I'm Andrew. And yeah, your comment about putting in the URL, was that from the Jingo ORM? You're passing that as a comment in the SQL. So one of the hacks we do, to get interpretation is that we wrap the cursor inside Django's backend so we can add timers around it. And as part of that, we're already overriding it so we can just add comment at that point. So we have some horrific things. And there's a request thread locals, some of the horrific things that you shouldn't be doing. Do you have to inspect the cost stack to get the method near it? Oh, there's a middleware that sticks the request into a thread local and then I think, you shouldn't do this. I don't think we're doing that. Yeah, that's pretty accurate. The result is fantastic. The methodology is not so much. I want this stuff in Django. That one's going to go in there and delete our horrible monkey patches and be like much more pure now. But at the moment, it's more sort of just grungy, but it works. Okay, thanks so much. So you guys had some small ideas about code improvements that could go into Django. Where do you think there could be documentation improvements? There is like one of the frequently asked questions or some place buried in the documentation about small optimizations, but I don't even think they touch a single thing that you guys said in this panel. I mean, there is the caching framework. There is HTTP caching, but nothing that really glues those all together. And I know, Peter, you're working on a book about this was an awesome resource of the community, but where could Django be better about helping at least point people in the right direction for some reason? This is a problem sort of, it starts very much on this editorial, which is, I think the part five now, the point does exist, but for a long time was neglected a little bit. Like, you know, as you start with Django, this is wonderful narrative thread of the tutorial, brings you to all the ideas as a brief slide. It shows you like, this exists going in later, this exists going in later, and then at some point it drops off and goes, and here's the reference docs. And of course, I'm sure this is probably six years ago, and they were much smaller, but now, like, you know, even as part of migration, but they added like another, like couple of like 20, 30 pages of docs. So reading all of it becomes very difficult. I'm not sure what the best way to expose that is. Perhaps there is a call for some kind of more of like, advanced reading topics, or just sort of like a very brief summary of these other things that, like for a long time, people didn't know South existed. Like, South is this assumed thing in Django, but nothing on the websites really existed because it wasn't a fish, it wasn't an individual project. And so there was this weird thing where like every conference would be like, people were like, oh yeah, I used to do South on stage, but it was never any setting in the way. That figured itself eventually, but I don't know it is a problem. I think at some point there is some aspect of community involvement, or I think books and things are very bad. Like it was like docs, two things there, a learning resource and a reference resource. And Django is very good at the latter. If I wanted to find out what a field is, I can find it almost interchangeably, but as a learning resource, I think that there is an improvement you made. I think one hard thing is the Django docs are not opinionated, and I think that's a good thing. But I think when you get into this stuff, if you're learning, I think it's really good to have an opinionated resource. Like you don't wanna know that there's eight different whiskey servers that you could possibly use. You want somebody to just say, this is the good one, you should use this one. And I don't know if that's Django docs place to say things like that. So yeah, I mean, maybe it's third party resources that say, yeah, we've written a book that's doing basically this, but I think it was born out of, we felt like there was a need for an opinionated resource that doesn't belong in the Django docs. The Django docs should be pretty agnostic on how you use it and everything. So yeah, I think it's a challenge. And trying to cover all the bases is a monumental task. And then I think it was a big deal to get you whiskey into the Django docs. And now somebody has to maintain the you whiskey and the Apache. And I don't know if there's all this stuff. So maintaining all those different versions and then you drop the new user in and you say, well, you could do this or you could do that. Have fun. For about five minutes at Django EU, Russ and I talked a little bit about putting in like some automated checks that we've made absolutely no progress on. And I said that I was gonna work on it, but I just now remembered that I'd said that. So hopefully in the next couple of months, I'll get that done. But no, that looks for the very simplest common things like you're storing your sessions in the database, just a management command that you can run against your existing settings and say, well, you probably shouldn't be doing that. You should default. That's the default. Is to use the database, right? But that's appropriate for getting started, but it's really easy. And I've even done it on large production sites. I've forgotten to change that. And you can get 20% better performance across the board just by swapping out and saying use Redis or MemcashD. So there's lots of little things that are easy to forget. Whether you're using a cache template loader and things that are not, that are all in the docs, they're in the reference that tells you exactly that this will get you better performance or this shouldn't be used in production, but there is no quick easy, let me do a quick health check on my settings and see that, okay, I'm at least not doing the top 10 things that are bad. I might need to do 10 more other things that are never gonna, that are gonna be very site and project specific, but at least I'm not doing the 10 easy, easy to fix things. Gross. Sorry, I can't imagine the one situation in Tango County you could have had anything to do with the fact that you've forgotten what we were agreed that we were gonna do. There are those multiple places where you can be attacking sort of performance and scaling issues. There's always the code stuff that you use an order one algorithm, not an order n squared algorithm and that sort of thing. But then at the DevOps side, at the beginning you said, you did make the point about these are quite often problems you'd like to have and you don't necessarily have to deal with them. There are vendors now who are out there like Heroku and Gondor and whatnot that sort of talk about the DevOps and we'll just make the DevOps problem go away and if you have load problems, just turn this knob and we'll charge you more money and everything will go away. How much of that is snake oil? How much of that is convenient when it's small, useful when it's large and how do you determine when you cross that boundary? As someone who's written a service like this. So a lot of the advantage in platforms like Heroku and stuff is that they're very architecture forces you to write scalability. So Heroku forces upon you several different strengths which you wouldn't have by default on your own system which are things that are more scalable. Like things like lack of a rightable data file system. Scalability thing. Things like your things aren't guaranteed to be on the same machine. But they enforce whole different types of constraints like the way things boot up and run that naturally makes the whole thing like horizontally chargeable to some extent. I think that part is not snake oil. I think the turn the knob make it fast thing is a little bit like that. Especially because some problems aren't solved by just adding more servers. Especially ones that are constrained by sort of cross talk and cross-trait-based access. In particular, like, so Heroku post-credits I think it's almost the better product than them because that actually does do a lot of stuff with post-credits that is very useful and tricky to do yourself. Like things like having followers and that kind of stuff. But similarly, you can't just at some point expect to make your website magically faster. If someone says they can do that, don't trust them. They're sending you a lie. Some part of it won't be true but the entirety is probably not true. It's always hard work with all the millionaires. Yeah, I mean, if those services really could just dial up the knob, Peter wouldn't have a reason to have written a book and we wouldn't have a lot of clients. No, you can get really, really far. It just gets very, very expensive. And at a certain point, the ROI, both in terms of kind of the flexibility to use the tools you wanna use on the opposite dev side and then just the sheer cost of those services make it cost-effective to dedicate a person to look into these things for three months or hire somebody like us to come in and do stuff for them. You can get very, very expensive, very, very quickly with those services by just dialing up the knob. Yeah, I mean, like the, if you properly, once you're beyond a single server, you have, which is, again, like this is kind of what is enforced by Heroku. You have your database server, you have your app server and you have your static files getting served someplace else. Going from that to auto-scaling your app servers, which have no state in them, is pretty easy. So going from one server to, well, maybe not one, but two servers to five to 10 to 100, that's easy. But all you're doing is pushing your pressure lower down the stack. So if you're scaling with two servers and there's no pressure on your database and then all of a sudden, oh, my app servers are overloading and I need to add 50 of them now, that same database isn't gonna handle that traffic, probably. So you pushed it down your stack and now you need either a bigger database or multiple databases and that's not as easy a thing to just turn the knob on. You require some kind of logic and stuff there. So yeah, I think on your stateless layer, auto-scaling makes a lot of sense and works, but it doesn't get you. And sort of pushing things down, you can go further, at some point there are sites where the network engineering is a critical part. Sure, you're absolutely gonna have the throughput, you have all the files, the network engineering, like the IP addresses, the unicast, the bandwidth, the throughput, the topology, that's the bit where the pressure is. And so you can't expect one solution to fit all problems. Like you've got things like Netflix is a very different kind of problem, for example. They serve static content that's very easily shotable. We have to do transactional checks and sell the exact number of tickets and then stop. But we have a very spiky load, Netflix have a very particular rampy load. They're different challenges. Like if all websites are the same, I suspect that this problem might be more solved, but it isn't, which is kind of fun for us anyway. I'll throw one more on there. In the big data space, there's a big problem about knowing exactly what big data is. I have a big data website that contains up to one gigabyte of data. There's a similar sort of thing here with performance where people say, you know, I've got a really, really high traffic website. I've got to deal with like four or five customers hitting me three or four times a second. Where do you go to draw the line of the sort of sites? What do you think of as a high traffic site that you actually need to start and really seriously thinking about these problems versus, you know, okay, yeah, you might have a bit of traffic but you really should be able to do that on just a single server and not worry about all this other stuff. So I think it depends on the type of site. So I've run a site that got 4,000 requests a second before one server because it was a very simple form of static and at the same time, the same number of requests in the event where it takes an entire cluster because it's in a very different kind of load. So I think it's not necessarily the number of requests a second. It's a lovely number to wave around. It's not that important. Like, you know, I'm sure CDNs get a lot more than anybody else does and that's, you know, a very different kind of load. Although it's also a different job where we're not saying they're easy to write. But I think it's the case, it's almost a team thing. Like the point where the growth and the speed start outstripping your ability to code up to it easily, I think that's the point where things change. Like where a small team of a few people was no longer enough to keep up with an increasing load where like you're constantly firefighting. That's almost for me, more of a turning point where suddenly like you need an ops department, you need a separate sort of like QA department or whatever. Like that's the breaking point. Yeah, so again, as with monitoring that the resource utilization or your machines, you can even monitor or pretend to your team or your ability to cope. Like at some point you're doing okay and it's linear and at some point you can see that you're not coping fast enough so at that point you need like a quantum leap. You need to change either by hiring more people, using different services, using different technology or something. So you can identify those points and unfortunately no one can tell you what the right solution for that would be unless you give them a lot of money. But that sort of, this metric will identify like where it needs to happen. If you see that you're still doing okay and you still have time to develop new features, you're okay, you don't have to go looking for anything else. If you see that I'm still able to do that but one month from now based on the curves I will not have any free time to actually develop the features, you need to do something. And it's a pure and simple business calculation like do I want to spend more money? Do I want to spend, hire more people? Or do I want to hire a consultant? Or do I want to spend time and investigate a better solution? Maybe a change of architecture, maybe change of features, whatever. I think there's very, very few sites that get to that phase that you're talking about or should be at that phase. I think a lot of people like to think they are or like to think that their site is this unique flower that can't be handled by any tools that normal men have made, men and women. And it's learning more about your stack and your tool set can buy you so much time. You find that one knob in Postgres or in Varnish or whatever that you turn and it's like, oh my gosh, I just doubled my throughput just by learning how my tool set works. So I would say you're at that point of scale is a major issue when the standard toolkit no longer serves your needs. And you really do have to invent new things. I don't think there's many websites that really get to that phase where the standard toolkit. Cool, and we're out of time. Thanks everybody.


What is going on guys welcome back to the channel critical overlord here in this video I want to talk about what I think should happen in regards to the furthering of the Jeepers creepers franchise as many of you know The creator of this series is writer and director Victor salva He has a bit of a troubled past a little some color more than just troubled very controversial stuff in regards to several things that occurred behind the scenes of one of his films from the late 80s I believe was called clown house Still to this day to play his career due to the fact that now that we have the internet people are able to look things up They're able to find stuff out a lot more put them in the light Or as opposed to in the early 2000s when the original films came out No one really had the internet the internet wasn't as big no one was really searching a lot of stuff But now with the way things are today everything relies on the internet people are active more active on the internet So you kind of have this issue now where it's harder for him to make movies now without having any backlash Because of the fact that the internet is such a big deal now That's not making any excuses for any of the heinous things he did in his life Me personally, I'm the type to forgive and forget especially considering the fact that I do not know or Nor am I aware of what he has been doing since then but everything that I am known or what has been provided in front of me of Gives me the sense that this man has turned his life around Maybe not entirely, but he at least hasn't done anything that heinous since what occurred in the late 80s So with that being said Jeepers Creepers 3 had a tough time getting started basically due to his background and the fact that that background wasn't becoming more More of popular on the online there were threads talking about it several stuff because many people were unaware of Aware of this when a when he initially did the first two films So when the third film was trying trying to get made his background was one of the reasons hinted at for not being For being one of the reasons the third film struggled to see the light of day It's the reason why the third film had the budget that it did I don't think too many people wanted to work with him from reports that came out another thing that's been a Hinderance in regards to Victor Salva is that with him being attached to it Jeepers Creepers 3 There were people attached to the project and then for whatever reason they just dropped out I don't know why that is but Someone has it's not hard to assume that it probably has something to do with Victor Salva's past And it's easy to understand why why these actors or actresses wanted to step down Everyone's entitled to their own opinion and what they feel is best for themselves But by no means do I think that someone who decides to work with Salva is Condoning any of the acts he did in his past because they're making a movie. They're not doing what he did in his past That's not what's being done here. They're out here making a movie now Some people are willing to overlook that and put their differences aside And collaborate with the gentleman to make this movie possible. Some people are not They think what he did was very unforgiving and I can understand that to a degree but Personally if we are ever going to see a Jeepers Creepers 4 or anything else regarding this franchise I think Victor is going to have to Come to terms with the fact that he needs to sell the rights or somehow get the property in someone else's hands Because I feel like the backlash would be kind of decreased a little bit if he's not the one that's full That's like shoehorning this project or Piloting it rather I feel like they I feel like if Victor lets someone else take over someone close to him Someone that he trusts I feel like they can do something great with this series. Once again I feel like we can have a film that gets a decent budget Stellar cast stellar productions that stellar visual effects bring the creeper back to his mysterious ways And also adding to that Victor I think he has he hasn't done any other projects really outside of the Jeepers Creepers films that have made him so known and I think that's probably one of the reasons why his past came back to bite him because he made us He made a film in the early 2000s that has gained a very big cult following since its release and it's well It's well appreciated amongst the horror community Many people still watch it to this day Everyone talks about the first two films and everyone talks about how bad the third movie was if we're ever going to see anything else Regarding the series I think he will have to just find someone to like take over the rankings from him Because it seems like no one wants to work with him The past is how tragic it is his past is never going to be he's never going to run away from this It seems it seems like his past is always coming up in a discussion somewhere and to a degree That kind of makes me a little upset not because I don't think that he should be getting be little like this Maybe some people do take it too far, but it's just a simple fact that he create He did create a character here that has potential to be explored and we just can't do it Because of his past and I feel like if he wants to let the fans get what they want out of this character If in some way possible He should try to find somebody to take over and I don't I don't think it's that he's not trying maybe He isn't and simply no one wants to be involved with the project that he created So what that means said I'm really hoping that we do see something else from this property in the near future but if it's ever going to be up to the The status that the first two films was first two films were with a somewhat decent budget of around maybe 10 to 12 million dollars I think Victor Salva would have to step down a bit. He can still write the movie I don't want anyone else writing the movie, but for us to fully get what we want as fans I think Victor is gonna have to step down in some capacity because not too I don't think a lot of people want to work with this gentleman Nest is just a sad truth because I think the creeper is a unique character and there's a lot of potential here Let me know what you guys think about this down in the comment section below Do you agree or do you think the series should just die as it is me personally? I'd be fine if they never made another film because the third movie put such a bad taste in my mouth But let me know down in the comment section below what your thoughts are in the description I'll have links on my social media accounts about Facebook Twitter and Instagram If you haven't already make sure you subscribe to our post notifications, so you never miss a video I will see you guys in the next


The Stop COVID-Dets shorts make it easier for you to go to the presentations that you are interested in. I'm Dr. Raymond Sarmiento, Director of the National Telehealth Center. And I'm Dr. Susy Pineda Mercado, Adjunct Faculty of the National Telehealth Center. Together, let's stop COVID-Dets. Thank you, thank you for inviting me to be a panelist in this session on Limited Face-to-Face School, Ligtasba. Let me start by introducing UP2U. We've been talking about UP all the time but UP actually consists eight constituent universities across the country and there are 21 campuses across the country too. And we have more than 54,000 students and UP Manila is the Health Sciences Center of the University of the Philippines system. You can see in the right side that under UP Manila are actually we have degree granting units and we have non-degree granting units and for the degree granting units we have a list and everything in red is actually practically a frontliner and you can see that among the non-degree granting units of UP Manila will be our PGH and the National Institutes of Health. So let me talk about Limited Face-to-Face now. I really am looking at my degree granting units now and everything in red actually needs a certification from CHED to be allowed to do the Limited Face-to-Face. Now, when you talk about UP Manila, there are several levels of safety we're talking about. We're talking about safety to the health workers first, safety to the patients and the general public and then safety to the non-PGH and non-NIH employees and that will mean the faculty, the students and the staff. We're practically in one compound. So from Pedro Hill to Padre Fawra, that's UP Manila. So every time there is something that's happening in PGH we must be aware because we may be affected. Now, I'd like to show this algorithm because one thing I've learned actually in the past almost two years now is that having a visual algorithm for our people on what to do is very crucial. So if I can just walk you through this algorithm. So here is a poster that we actually have in the internet and distributed. There's a question what to do if you think you have COVID-19 and you can see there's a question whether you have symptoms or high risk and there's already an advice, isolate. The third is to report your symptoms to BES. So let me introduce the BES. BES is actually an app developed by Raymond, our host. We're in through the cell phone or the computer. You're able to actually list down your symptoms and what will happen now is that it's going to go to a supervisor level as to whether what kind of symptoms you have. So the BES has been very useful for us here in UP Manila and then eventually the advice is to contact a focal person and next slide I'm going to talk more about the focal person and the last will be to contact actually the University Health Service or our hotline number. So having a visual algorithm actually is very helpful for the general population because they know what to do. They don't have to look for it. Just save this sheet of paper. Now I show this list, this table actually. We have a table with names but basically what we've done is that we do have an overall nurse coordinator for COVID concerns. I'm not talking about PGH, I'm talking about the rest of the UP Manila community and we noted that every college has admin staff, faculty and students so we actually put in a person in charge which means if you have the symptoms then you have a person to talk to and every day the Chancellor and the Vice Chancellor for Administration actually inform if there is a positive case and if I have a Dean who is symptomatic I'm also aware because they answered the best. So this system has been very useful for us in Administration and I felt that the anxiety has actually toned down. Now moving on now to the guidelines. If you notice this is dated August 2020 but you really wanted to open already in August 2020 we've been preparing for this but as you can see here now if you look at my list on the left so far we have five who have given have been given approval College of Pharmacy and SHS Palolete are now in the line of being hopefully accredited very soon. If I may just mention that the School of Health Sciences has four campuses one in Palolete, Coronadal, South Cotabato Baler Aurora and we just opened Tarlac Tarlac so let's take a look na on what has happened. Of course just like anybody else we had to meet with the mayor and the LGU approval. Of course we had to go through a process of being visited by a team from CHED and here we received our award on July 14 of this year. We were quite excited about it because for a year we've been waiting for this time that we be allowed to start the limited face-to-face. Now so these are the colleges have been to offer the face-to-face college of medicine college of nursing college of dentistry college of public health and college of medical profession so each of these colleges were visited by a team from CHED and a team of experts from different universities. Now instead of presenting every college I've actually grouped them because there are some general policies and guidelines that's actually shared by all and as you can see that as early as July of 2021 we've been finalized and vetted by administration at UPI system and at the same time it has been revised many times to make sure that it is appropriate for all of the colleges. So of course number one is still the vaccination there's a very, very big push and I just cited a few that have been significant to the success of the vaccination. College of medicine right now has about 99% vaccinated of allied medical professions has about 100% and then for the college of nursing for incoming third year it's also 100% and for dentistry about 95%. So in other words when you say vaccination now we have many partners anywhere from PGH, LGUs as a matter of fact medicine partner with Santa Ana hospital to bring in their interns and medical students and very recently we had the bacuna bus from the Philippine Red Cross. So let me just walk you a few things that have been done by all of the colleges I will only show you a few pictures so we had to actually insult a lot of the electric plants and we had to put all the signages you can see here but you know whereas in the past you didn't really matter where you passed but we've got all of these arrows we've got lines for exit and the entrance and then in every college now you will have this temperature measurement as well as the alcohol at the beginning actually in front of every room you also have this every room so you cannot just enter a room now without having gone through the precautionary measures. So we've been able to we started looking at the spaces and then over there no people yet but the thing is you can see here that this is a cafeteria that's supposed to be open anytime now and then we also have outdoor eating spaces that we've started to identify again with the precautions of spacing and physical distance and so on. We do have the isolation room so this is so we have four students with the capacity of four students two at the college of nursing and two at the college of public health to service all the students or staff or faculty who may actually turn out to be symptomatic during a class. So let's just walk through some of the colleges and see how you know how they look like so this is a college of allied medical professions for physical therapy occupational therapy and speech therapy and as you can see at the beginning they had a lot of they practiced and a lot of simulated patients actually but they actually started already the face to face and you can see the distancing even with the parent and the buyer that have been put in place. So whereas in the past this would be full of students and patients now they have been scheduled depending on how it will be allowed in the room despite the fact that we have many students many patients now they have to line up because they have to follow the schedule of the you know the cyclic the cyclical shift of four days and the 10 days rest and as you can see here again they actually use the app of best because every student must know if she is symptomatic must not go to the office and if ever she is symptomatic then the teacher will actually know and then they know how to start the tracing in that particular class. Going to dentistry which I was sharing with the group in the most expensive college we just for the retrofitting of the classes and I'm not even finished yet we have spent 19 million just for the HVAC of the clinical rooms you can see here that there are no barriers here in this laboratory the students have come in here when they were actual patients they were using actually the mannequins here as you can see here now it's the same whereas before this was you know next to each other you've got the physical barrier and there are a lot of visuals actually all over the place to remind the students on what to do in the case when they're seeing patients and the other thing is that we've got a lot of mobile acrylic barriers every classroom actually has S2 and to make sure that we provide additional protection now this is the memorandum that we're following specifically for dentistry requiring that the students, the faculty and staff would have the tests done three to five days prior to the start of classes now going to nursing same as the college of allied medical professions they do the four days face-to-face and the ten days of quarantine the second thing is that we have smaller classes now very limited and timed and with the regular self-monitor reporting even during at the time of they have the class one thing that's interesting here is that after every application activity they have a debriefing so well not face-to-face but still virtual but the important thing is that they get to see what's happening to the faculty also and to the students now for medicine now of the many activities of medicine I will only highlight two actually and that will be for anatomy and internship for every level there are specific set of activities but let me start with anatomy so for anatomy whereas in the past you have a room full of students and the cadavers lined up you can see here that now they are also scheduled they already had their face-to-face a projection for medicine and you can see that the Dean Dean Charlotte Chong actually at the beginning of the pandemic bought virtual digital dissection stations so they have to think fast because we could not stop producing the doctors and this became very handy at the beginning of the pandemic so life went on at the college of medicine moving on to internship they started the skills workshop on open air they following all the protocols before they went to the clinic but right now we already have interns rotating in PGH and as a matter of fact if I just list some of the things all the interns are actually vaccinated with one person people give a waiver there are clinical rotations they participate already in non-COVID areas again they use the app to make sure they don't have the symptoms they have the symptoms they have to consult and they have to follow the protocols and as you can see that if everybody become positive that administration takes care of helping them I show this picture of Dean Chong Dean of the college of medicine actually showing her teaching an intern during the rotation at ORL so this is what the students are missing the real opportunity to be able to see the patients not only in the wards but also at the operating room now in the last for the college of public health in addition to all the things that I mentioned the college of public health was actually designated by CHED to establish the public health experts group and as a matter of fact they assist other state universities and colleges on the proper guidelines and in preparing them for the face to face so they actually have been training evaluators nationwide and they also participate in visiting the schools so in summary there are things that are common to all of the colleges and there are things that are peculiar to a particular college so what's coming up while college of pharmacy is about to open they're ready and we've just made an appeal and the school for health sciences is being visited by CHED right now and the South Coronadal and Baler have actually applied already for their possible accreditation does this mean that we're ready we do have challenges so let me mention some of the challenges major challenges because I have a lot of minor challenges first challenge is the safety during travel to the campus whether you like it or not we don't have enough beds for them we don't have we cannot accommodate we cannot do a bubble for them so even if I keep this campus safe then I still have the problem of their safety coming to school and the third bullet is something that we really have to consider once we start the face to face we have to establish the protocol we know that when a patient becomes positive we have an isolation room but what about the other students who are exposed so we're just now finalizing the protocol because we do have a guideline now we're in a student then the whole class is to be managed not just the student who turned out to be positive so let me answer the question ligtas na ba sa UP Manila now people say that because we have PGH then we should have the fear but to be honest because PGH is within the campus they have actually come up a lot of guidelines that we have been able to to actually use in the setting the academic setting and since everybody is careful then now we're no longer scared that we're actually within the same campus breathing the same air as the Philippine General Hospital so with that I want to thank again TVUP for considering the face to face limited face to face as one of its topics today Maraming salamat We hope that you learned as much as we did from that excellent presentation We also hope that you will join us every Friday from 12 noon to 2pm Manila time on Zoom, Facebook, or YouTube So stay safe stay connected and see you online


From New York, it's theCUBE, covering Blockchain Week. Now, here's John Furrier. Hey, welcome back everyone, this is theCUBE. I'm John Furrier, the host. We are in New York City for Blockchain Week NY for New York, part of Consensus 2018. A lot of activities happening. And I'm here with Agni Kazakukaiza, who's the president of the Vilnius Blockchain Association. Did I get that right? Your name? Yes, that is correct. Agni Kazakukaiza from Vilnius Blockchain Association. Thank you for coming on. Appreciate taking the time. First of all, I got to say, I love what you're working on. So, you've got this really cool project. Take a minute to explain what the crypto rally is. It's really cool. What is it? Sure, so crypto rally is an innovative concept. In short, it's Formula One meets Davos. It's a marketing platform for blockchain companies to showcase their innovations, what they have developed in blockchain technologies. It's a car racing event. First, it's starting in Lithuania, and then we're going to Dubai and China, taking our partners and sponsors together with us. And they receive a huge global media exposure by participating in crypto rally. So, the purpose is to take the cars and travel around and do education, is it inspirations to partying? Is it fun? What is the format? What is the format? So, the format is we're traveling from Vilnius to the seaside and back. And crypto rally stops in six pit stops. In those pit stops, we have performances, car drifts, drag races. And the blockchain companies showcase the innovations. Let's say, automotive blockchain company that is installing sensors in the cars. They can showcase how it actually works. See, it's a blockchain company that opens the wallets for customers. They can open the wallets there and then. Yes, of course, it's a party. We have parties, we have 3D projections on the walls. We have augmented reality games. All of this is interactive experience for the blockchain companies and for the community to participate together. And it's going to be fun, it's informational, educational. Where did the idea come from? It came, it was my idea actually. I worked before with Formula One teams. We consulted them and understand the concept quite well. Actually, it's a racing event. But in a sense, it's a marketing platform. You put stickers on the cars and if you can call it circus, travels around the world, giving immediate exposure to the companies that participate in it. And cars just add a sexiness to all of this event. That's beautiful. What's involved? Can you talk about the names of people that are involved? Sponsors and communities? Yes, of course. Pilaio's already participating. We have local partners, CoinGate, who actually are installing cryptocurrency payments all along the route of Crypto Rally. So wherever Crypto Rally goes, each country will be cryptocurrency nice. This is a treasure hunt, meets car racing, meets partying, blockchain style. Exactly, it's really, really fun. So what's your background? How did you get into this? I mean, this seems very cool. Yes. I mean, I love it. Thank you very much. My background is in finance. I studied in London, investment and financial risk management. Worked in investment bank for a little bit, then consulting company. And now I'm doing a master's degree in blockchain. I believe it's a great opportunity for our generation people to make a huge impact to the world. I'm so excited about this new era. I can't contain my happiness. I love your story. I think it's phenomenal. Thank you. I think your dynamic, vibrant, super smart. But I look around here at the hotel to see a man. We need more women in tech. Tell all your friends. Exactly, exactly. So we're trying to change that. The crypto rally team consists girls. Actually, our partners is Emily and Gaila. So three of us founders were female. So we're changing the whole blockchain ecosystem. Thank you so much for doing it. Thanks for coming on and sharing. Love to go along for the ride. Take the cube with you. Maybe we could be media partner. We'd love to promote it. Keep in touch. Thank you very much. Thank you for coming on. Thank you. The cube, crypto rally. The cube, we're rallying here. Day one of two days of coverage. We were at, get eight interviews last night at the crypto house. This is blockchain week in New York City. We are rallying the crypto rally. Check it out. Is there a URL that can go to crypto rally? Yes. Website share the address. CryptoRally2018.com Check it out crypto rally. This is the cube rallying in New York City. We back with more coverage after this. Thanks for watching. I'm John Furrier.