fb547f24d9
All checks were successful
deploy / deploy (push) Successful in 48s
Instead of fetching up to 50k inventory snapshots (~442MB), scope the query to only the time range of the current submission batch with a 15-minute buffer. For a typical 1-hour batch this drops from 50k rows to ~300 rows, well within the 1280Mi pod memory limit. The coalesced_at_idx on intent_inventory_snapshots covers the BETWEEN clause so this remains efficient. Proof: history-writer OOM kills from refreshQuoteOutcomes inventory fetch Assumptions: 15min buffer covers the attribution window for all submissions Still fake: heuristic gap outcomes may attribute trades imprecisely
20 lines
715 B
JavaScript
20 lines
715 B
JavaScript
import { createPostgresPool } from './src/lib/postgres.mjs';
|
|
import { refreshQuoteOutcomes } from './src/lib/postgres.mjs';
|
|
|
|
async function main() {
|
|
const pool = createPostgresPool({ connectionString: process.env.POSTGRES_URL });
|
|
|
|
console.log("Running refreshQuoteOutcomes...");
|
|
try {
|
|
const records = await refreshQuoteOutcomes(pool, {
|
|
btcAsset: { assetId: 'nep141:nbtc.bridge.near' },
|
|
eureAsset: { assetId: 'nep141:eure.omft.near' }
|
|
});
|
|
console.log("Records length:", records.length);
|
|
console.log("Completed:", records.filter(r => r.outcome_status === 'completed').length);
|
|
} catch (err) {
|
|
console.error("Error:", err);
|
|
}
|
|
process.exit(0);
|
|
}
|
|
main().catch(console.error);
|