Making the slow parts fast
Finding the queries and the missing indexes behind a system that has got heavier every year, and fixing the ones that matter.
30 days of electricity data in 180 ms
Engineered hourly electricity‑consumption aggregation variants in Python, SQL and Bash + Jq, with the Python benchmark processing one 30‑day JSONL dataset in 180ms.
Built and benchmarked electricity-consumption aggregation in Python, SQL and Bash + Jq; Python processed a 30-day JSONL dataset in 180 ms.
Made a geographical data pipeline 50x faster
Recorded a 50x geographical data‑pipeline improvement in the founder’s Utiligize work through SQL and data‑model changes across PostgreSQL, MS SQL and Google Cloud BigQuery.
The founder records a 50x geographical pipeline improvement at Utiligize through SQL and data-model work across PostgreSQL, MS SQL and BigQuery.
Improved GIS map performance 10x on Postgre
Improved geographical map application performance by 10x through strategic database transition from MSSQL to PostgreSQL, including the data cutover, optimizing processing and data security.
Improved a GIS map application 10x by migrating MSSQL to PostgreSQL — spatial queries dropped from 2.5s to under 250ms.
Ran 100 Postgre, MS SQL, BigQuery warehouses
Architected, created, and managed 100 PostgreSQL, MS SQL, and Google BigQuery data warehouse databases with primarily GIS and time‑series data, optimizing performance and scalability.
Architected and ran 100 PostgreSQL, MS SQL and BigQuery data-warehouse databases for GIS and time-series data — query times down 40–60%.
Accelerated Postgre performance by 10x
Accelerated PostgreSQL performance by 10x via strategic indexing, partitioning, and query optimization, enhancing database efficiency for user, tenant, geospatial, and time‑series electrical data.
Accelerated PostgreSQL 10x via indexing, partitioning and query tuning for user, tenant, geospatial and time-series data — resource use down 40%.
Time‑ keys for a growing data model
Adopted UUID v7 time‑ordered identifiers (PostgreSQL 18) as entity keys to reduce B‑tree index fragmentation and speed up queries.
Adopted UUID v7 time-ordered keys in PostgreSQL 18, aiming to reduce B-tree fragmentation and improve inserts and range queries for entity tables.