Mpampis Kostas

184 posts

Mpampis Kostas

@charkost

Back-End Rails Engineer @SkroutzDevs

Athens, Greece Beigetreten Ekim 2013

500 Folgt243 Follower

Mpampis Kostas@charkost·9 Oca

The new year finds us with a new feature for lightning-fast debugging sessions @SkroutzDevs - Breakpoints in Production HTTP Requests engineering.skroutz.gr/blog/breakpoin…

English

188

Mpampis Kostas retweetet

Nate Berkopec@nateberkopec·12 Eki

How to be a top 10% Ruby perf team: 1. SLO-based queues 2. RMP in all environments 3. RUM in browser 4. Autoscale web and worker 5. Instrument request queue time 6. Automated alerts/SLOs in Terraform 7. Prosopite/strictloading in tests 8. Latest Ruby w jemalloc 9. Turbo

Nate Berkopec@nateberkopec

One of the ways I assess the "performance savviness" of a team is "are they running rack-mini-profiler in all environments, including production?" RMP remains the flagship tool for any organization serious about performance. Running it in prod means that you can replicate almost any problem.

English

168

16.1K

Mpampis Kostas retweetet

Nate Berkopec@nateberkopec·1 Eki

Tired: eager loading suggestions Wired: prosopite, raise exceptions in all environments except prod if you N+1

English

3.5K

Mpampis Kostas retweetet

Nate Berkopec@nateberkopec·20 Eyl

These gems are fine, but IME 90% of N+1s in apps cannot be fixed simply by adding a preload/eager_load in the right place. This is why I prefer "fail hard"/andon cord approaches like prosopite, which doesn't propose that it always has the solution

Yuri Sidorov@YuriSidorov

@nateberkopec Doesn’t `jit_preloader` gem fix that? github.com/clio/jit_prelo…

English

4.4K

Mpampis Kostas retweetet

Nate Berkopec@nateberkopec·6 Eki

The CGRP Slack's favorite Ruby performance gems: github.com/pganalyze/pg_q… github.com/ankane/pghero github.com/nevir/Bumbler github.com/plentz/lol_dba github.com/charkost/proso… Buy any of my books/courses to get access to my Slack. It's often my reader's favorite part!

English

119

11.7K

Mpampis Kostas@charkost·18 Ağu

@nateberkopec @techpickles He is also a frequent contributor to the open source tools he set up like prosopite :)

English

119

Nate Berkopec@nateberkopec·17 Ağu

.@techpickles is a dev-env whisperer. Since he joined Gusto 2 years ago, I think 90% of my time is spent using and interacting w/tooling he either set up or wrote. He makes the monolith a much nicer place.

English

4.1K

Mpampis Kostas@charkost·28 Haz

@nateberkopec Thanks again for the publicity! Apart from dev+test envs, we are also running it in the production http traffic of @SkroutzDevs with a 5% request sampling & custom logger to Sentry.

English

260

Mpampis Kostas retweetet

Nate Berkopec@nateberkopec·28 Haz

Prosopite continues to impress; github.com/charkost/proso… The functionality of running it in tests is quite good.

English

7.1K

Mpampis Kostas retweetet

Josef Strzibny@strzibnyj·14 May

Ruby 3.3.0 YJIT improvements 🎉 I like the idea of starting YJIT only after your application fully booted. Also exited to see a pure-Ruby JIT RJIT.

English

5.3K

Mpampis Kostas retweetet

Thomas B@ThomasOneDev·21 Nis

@SanchezDav90 @andrewmcodes @rubyforall I had an issue with bullet talking way, way too much overhead. I’m talking over 90% of the time spend for bullet. I replaced it with prosopite. It does the same and no visible overhead. My crazy went from 15 minutes to 1 minute (it does a lot I know)

English

158

Mpampis Kostas@charkost·9 Mar

@_pawurb Hello @_pawurb, prosopite author here. Could you please provide some examples of the many false positive cases you've seen it report?

English

Mpampis Kostas retweetet

Gavin Morrice@iamtheantislop·9 Ara

@charkost Thank you for the feedback. I actually have a gem that uses Prosopite to automatically detect n+1s and report them on GitHub pull requests: github.com/bodacious/jimi… The intention for this article, though, was to cover the basic principles. So tools were out of scope 🤓

English

Mpampis Kostas@charkost·9 Ara

@MorriceGavin Nice post! One option apart from manually checking the rails log for identifying n+1 queries is to use auto-detection gems like Prosopite and save a lot of time :) github.com/charkost/proso…

English

Gavin Morrice@iamtheantislop·7 Ara

My latest post on Cookpad’s developer blog—Source Diving—discusses some of the issues trickier issues around n+1 query problems 🕵️‍♂️ sourcediving.com/understanding-… #ruby #rubyonrails #webperformance

English

Mpampis Kostas retweetet

Nate Berkopec@nateberkopec·8 Kas

That heart-sinking feeling when you see a huge performance regression but it wasn't tied to a code deploy 🙃

English

Mpampis Kostas retweetet

Nate Berkopec@nateberkopec·1 Eyl

we've been using Prosopite at Gusto for a minute (implemented by others, not by me) and it's a significant improvement on Bullet. Check it out: google.com/search?q=proso…

English

Mpampis Kostas retweetet

Xavier Noria@fxn·24 Tem

In OSS, there are no sprints, stand-ups, retrospectives, 1:1s, 360s, quarters, velocities, estimations, deadlines, project managers, "how is this going", year goals, ..., could go on and on. Yet it ships non-stop and runs the world.

English

131

761

Mpampis Kostas@charkost·12 Tem

The N+1 Dilemma - Bullet or Prosopite? labs.factorialhr.com/posts/bullet-o…

English