brenogazzola

# Rails + PostgreSQL Performance Audit Playbook

A field-tested method for finding what's actually burning your database CPU, built for a
Rails monolith on managed PostgreSQL (Cloud SQL / RDS / etc.). It assumes no APM — just
`pg_stat_statements`, `pg_stat_activity`, and discipline. It pairs well with an LLM: point
one at this file plus your query results and let it do the attribution; the queries below
are ordered so a human can run them and paste results back.

## The core idea

Brayden

#!/usr/bin/env bash
set -euo pipefail

bold() { printf "\033[1m%s\033[0m\n" "$*"; }
info() { printf "• %s\n" "$*"; }
warn() { printf "\033[33m! %s\033[0m\n" "$*"; }
err()  { printf "\033[31m✗ %s\033[0m\n" "$*" >&2; }
ok()   { printf "\033[32m✓ %s\033[0m\n" "$*"; }

require_macos() {

jmschneider

## SqliteFullTextSearch Concern
#
# The `SqliteFullTextSearch` concern provides a set of methods and triggers to enable full-text search capabilities for ActiveRecord models using SQLite's FTS5 extension.
#
# ### Key Features
# - **Full-Text Search Scope**: Adds a `search` scope to the model for performing full-text searches.
# - **Index Creation and Management**: Automatically creates and manages FTS5 tables and triggers for the model.
# - **Attribute Configuration**: Allows specifying attributes to include in the full-text search index.
# - **Trigger Management**: Sets up triggers to keep the search index up-to-date with model changes.
#

luizkowalski

#!/usr/bin/env ruby
# frozen_string_literal: true

# Lives in .kamal/update

require "json"
require "net/http"
require "uri"
require "yaml"

bensheldon

In my application every time I send a newsletter to a User, I create a NewsletterDelivery record. I frequently want to be able to query, for each user, what is the most recent newsletter delivery record. This is called a "last n per group" query and a LATERAL JOIN is the best way to do it imo. But the query I've been using (and I've told people to use, and seen blogged about) is not very good, because the conditions don't get pushed down into the subselect which means that the query ends-up lateral-joining all the records before it applies the conditions for the association.

Instead of doing subselect_table.* the better query does association.id AS assocation_id, subselect_table.id, subselect_table.title, .... and enumerates over all of the columns. This allows the association query, which Active Record tacks on at the end as WHERE association_id = $1 or WHERE association_id IN ($1, $2, $3, ...) to be pushed down c

joeldrapper

[
	{
		"context": "Editor",
		"bindings": {
			"alt-up": "editor::SelectLargerSyntaxNode",
			"alt-down": "editor::SelectSmallerSyntaxNode",
			"ctrl-cmd-up": "editor::MoveLineUp",
			"ctrl-cmd-down": "editor::MoveLineDown"
		}
	}

julianrubisch

<div data-controller="search">
  <div data-search-target="button">
    <div role="button" data-action="click->search#open keydown.meta+k@document->search#open keydown.ctrl+k@document->search#open" class="outline secondary search">
      <%= heroicon "magnifying-glass" %>
      <span>Search</span>
      <kbd>Cmd/Ctrl+K</kbd>
    </div>

    <dialog data-search-target="dialog">
      <article>

dhh

#!/usr/bin/env bash

# Abort sign off on any error
set -e

# Start the benchmark timer
SECONDS=0

# Repository introspection
OWNER=$(gh repo view --json owner --jq .owner.login)

kaspth

require "bundler/inline"

gemfile do
  gem "rails"
  gem "sqlite3"
end

require "active_record"
require "action_controller"
require "rails"

mediafinger

# filename: single_page_rails_app.ru
# RUN via: `rackup single_page_rails_app.ru`

require "bundler/inline"

gemfile(true) do
  source "https://rubygems.org"

  gem "rack", "2.2.9"
  gem "rails", "~> 7.1"