Benchmarking and Stress Testing

[MUSIC PLAYING] [WHISTLING] I mean, baselining and then benchmarking are two sides of the same coin. So because your baseline helps you establish what the benchmark is, but benchmarking or the act of benchmarking is in a lot of ways stress testing or load testing or doing simulation tests. So yes, those definitely are-- I mean, I hate to say it, but they shouldn't be considered best practices. They really should be normalized practice as you move through the development life cycle. But with the rapid pace of delivery, the demands that users have and our businesses have, unfortunately, we don't oftentimes have enough time to do enough benchmarking or enough load testing. Sounds like a no-brainer. It sounds like an absolute no-brainer. But it's a no-brainer. But I will tell you that you need tools, and so you can't effectively benchmark without a monitoring solution. Let me just say that. Let me cut to the chase, because we've been talking about monitoring this whole time. A lot of my clientele will have some sort of benchmarking taking place and somewhat separately might be using sysbench or hammerdb or even the TPC industry level benchmarks that are available to help them decide and see what their levels are. The sustainable levels are for their database. However, the monitoring solution is what helps bring that load testing or that benchmarking to life. Because now you have even more observability while the actual-- the load testing or the benchmarking actually takes place. So whatever interactions and whatever stresses are taking place within your database, they're going to cause granular weights. Everything that exacerbates itself into a real blown issue into database. Stuff that we have to tune. Guess what? You need monitoring. So otherwise you won't have that visibility. Generally speaking, it will-- the metrics that you're going to get are going to be like response time based, or how quickly the transaction arrives. So yeah, it will say that the transaction is slow when it's under this user load, but that's different than knowing why it was slow under that user load. And those reasons come to life when you have the monitoring sit behind it. And then even more than that. Right? What if it's a canned application, but now it's something in the VM. Or it's something in the host. That needs to be optimized. Certainly we need observability there. So I'm trying not to preach too much, but I want. No, no, no, no. It's good. It's good. What I was going to say was I was speaking with a chap Dennis, and he was talking about benchmark factory. And I'm just going to highlight that here at this point. A benchmark factory too. I, and it's part of-- Great utility. Yeah. Yeah. It's part of our Toad product line. Great utility. Yeah, it's great, great, great utility. Definitely worth checking out. I mean, you've been super generous with your time. I got to say. Thank you so much, and I look forward to speaking with you again. Thank you. You have a good one. Nice talking to you.