Skip to content

Update 479-designing-effective-load-tests.txt #162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 9, 2024
Merged

Update 479-designing-effective-load-tests.txt #162

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 10 additions & 11 deletions transcripts/479-designing-effective-load-tests.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@

00:00:42 This is your host, Michael Kennedy.

00:00:44 Follow me on Mastodon, where I'm at mkennedy, and follow the podcast using @talkpython,
00:00:44 Follow me on Mastodon, where I'm @mkennedy, and follow the podcast using @talkpython,

00:00:49 both accounts over at Fosstodon.org, and keep up with the show and listen to over nine years of episodes at talkpython.fm.

Expand Down Expand Up @@ -448,7 +448,7 @@

00:13:44 And as you're pointing out, they don't just hold down control or command R and just flicker the screen as hard as they can.

00:13:50 They they're they're reading and they're interacting.
00:13:50 They they're reading and they're interacting.

00:13:52 And so what you're saying is if you really want to say how many actual users, not just kind of a throughput number, but how many people using the app do you possibly expect it could keep working or right?

Expand Down Expand Up @@ -550,7 +550,7 @@

00:16:54 What was the problem?

00:16:56 I initialized the logger with the string info for the level rather than the enumeration dot info, which was an integer based enum.
00:16:56 I initialized the logger with the string info for the level rather than the enumeration dot info, which was an integer based Enum.

00:17:05 So the logging statement would crash saying that I could not use less than or equal to between strings and ints.

Expand All @@ -564,7 +564,7 @@

00:17:22 Create your Sentry account now at talkpython.fm/Sentry.

00:17:26 And if you sign up with the code talkpython, all capital, no spaces, it's good for two free months of Sentry's business plan, which will give you up to 20 times as many monthly events as well as other features.
00:17:26 And if you sign up with the code TALKPYTHON, all capital, no spaces, it's good for two free months of Sentry's business plan, which will give you up to 20 times as many monthly events as well as other features.

00:17:39 You did mention that the CSS and the, you talked about the AJAX, but I think also things like CSS images, JavaScript files, not JavaScript execution, but just getting the files, right?

Expand Down Expand Up @@ -832,9 +832,9 @@

00:28:03 Otherwise, it might just say invalid.

00:28:07 This portion of Talk Bython is brought to you by WorkOS.
00:28:07 This portion of Talk Python is brought to you by WorkOS.

00:28:10 If you're building a B2B SaaS app, at some point, your customers will start asking for enterprise features like SAML authentication, skim provisioning, autologs and fine grained authorization.
00:28:10 If you're building a B2B SaaS app, at some point, your customers will start asking for enterprise features like SAML authentication, skim provisioning, auto logs and fine grained authorization.

00:28:20 That's where WorkOS comes in with easy to use APIs that help you ship enterprise features on day one without slowing down your core product development.

Expand Down Expand Up @@ -954,7 +954,7 @@

00:32:26 It's just overwhelmed by.

00:32:28 But yeah, I don't recommend running 10,000 concurrents on a single laptop because it's going to run pretty slowly.
00:32:28 But yeah, I don't recommend running 10,000 concurrent on a single laptop because it's going to run pretty slowly.

00:32:35 It's going to have a bad time.

Expand Down Expand Up @@ -1048,7 +1048,7 @@

00:35:15 And, like, what does that look like?

00:35:17 And I think what confuses a lot of people is the first time they use Locust or JMeeter or one of the other tools, they get all these percentiles back.
00:35:17 And I think what confuses a lot of people is the first time they use Locust or JMeter or one of the other tools, they get all these percentiles back.

00:35:25 And they're like, oh, the 90th percentile response time is this and the 95th is this and the 99th is that.

Expand Down Expand Up @@ -1292,7 +1292,7 @@

00:42:59 And it's just sitting there idle waiting for the responses.

00:43:02 So I know you mentioned the show a few times, but like the N plus one issues and stuff like that for ORMs in particular is where you get those types of scale where you're, you should not be seeing that many SQL queries.
00:43:02 So I know you mentioned the show a few times, but like the N + 1 issues and stuff like that for ORMs in particular is where you get those types of scale where you're, you should not be seeing that many SQL queries.

00:43:14 It's so easy to do because you write the same code, get the things and then loop over some and interact with some aspect of them.

Expand Down Expand Up @@ -1560,7 +1560,7 @@

00:51:46 So you can see like all the traces, how long they took, what calls it made on the backend, what queries it was running.

00:51:52 Like OpenTelemetry is a brilliant way of doing that.
00:51:52 Like Open Telemetry is a brilliant way of doing that.

00:51:55 And it's not just Python.

Expand Down Expand Up @@ -1867,4 +1867,3 @@
00:58:42 Now get out there and write some Python code.

00:58:44 I'll see you next time.