joeharris76

Check Databricks Serverless CPU architecture and RAM

It can be insightful to know whether a Databricks Serverless SQL warehouse (or serverless notebook/job compute) is running on ARM (Graviton) or x86, and which generation. This also reports the memory available to the execution sandbox.

Here’s a Python UDF that detects all of this from /proc/cpuinfo and /proc/meminfo.

joeharris76

{
  "coverage": {
    "expected_cells": 24,
    "missing_cells": [],
    "present_cells": 24,
    "repetitions": {
      "clickbench": {
        "1.0.0": 3,
        "1.1.3": 3,
        "1.2.2": 3,

joeharris76

#!/usr/bin/env python3
"""Analyze DuckDB multi-version BenchBox results for the version-performance draft.

This script expects the 72-run matrix produced by run_version_matrix.sh:
- Versions:   1.0.0, 1.1.3, 1.2.2, 1.3.2, 1.4.4, 1.5.0.dev311
- Benchmarks: tpch(sf10), tpcds(sf10), clickbench(sf1), ssb(sf10)
- Reps:       3 per (version, benchmark)

It computes median metrics per matrix cell and writes structured artifacts
(JSON + CSV) for table population in version-performance.md.

joeharris76

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

# Run from repo root so all relative paths resolve correctly regardless of
# where the script is invoked from.
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
cd "$(cd "${SCRIPT_DIR}/../../../.." && pwd)"

# ---------------------------------------------------------------------------
# Matrix configuration — edit these to change what gets benchmarked.

joeharris76

joeharris76

{
  "version": "2.1",
  "run": {
    "id": "mcp_b5db4a85",
    "timestamp": "2026-02-12T17:24:19.361388",
    "total_duration_ms": 6511,
    "query_time_ms": 4718,
    "iterations": 3,
    "streams": 3
  },

joeharris76

                                                                                                                                                            
╭─── Claude Code v2.1.12 ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                     │ Tips for getting started                                                                           │
│                 Welcome back Jonny!                 │ Run /init to create a CLAUDE.md file with instructions for Claude                                  │
│                                                     │                                                                                                    │
│                                                     │ ─────────────────────────────────────────────────────────────────                                  │
│                       ▐▛███▜▌                       │ Recent activity           

joeharris76

Check if Snowflake warehouse is using ARM (Graviton)

It can be insightful to know whether a specific Snowflake warehouse is running on ARM or x86 CPUs.

Here's a Python UDF that detects this.

CREATE OR REPLACE FUNCTION detect_cpu_architecture()
RETURNS STRING
LANGUAGE PYTHON

joeharris76

{
  "$schema": "https://zed.dev/schema/themes/v0.1.0.json",
  "name": "Cobalt",
  "author": "Jacob Rus",
  "theme.translator": "Peter Marreck",
  "themes": [
    {
      "name": "Cobalt",
      "appearance": "dark",
      "style": {

joeharris76

The number of nodes in each Snowflake warehouse is obfuscated but not really a secret

https://stackoverflow.com/questions/58973007/what-are-the-specifications-of-a-snowflake-server

one part states the server EC2 instance type as "warehouseServerType" : "c5d.2xlarge",

https://select.dev/posts/snowflake-warehouse-sizing

it’s fairly well known that on AWS each node (except for 5XL and 6XL warehouses) is a c5d.2xlarge EC2 instance, with 16GB of RAM and a 200GB SSD.