rays
c9964778cb
SeaORM gives a SQLite pool one connection unless told otherwise, and connect() did not say, so every request, every scan write and every read went through it in turn. Twenty-five people browsing in the load tests (#133) got 50 requests a second out of 12 cores, the fastest answers in 3-30ms and the medians ten times that. SQLite now gets eight. In WAL readers run beside the one writer. Every transaction here writes first, so it takes the write lock or waits out the busy timeout for it; SQLite refuses at once only a transaction holding a snapshot a write has moved past, and none here does. Db::memory switches its file to WAL too, as Db::open does, so the tests share it as the daemon does. A test holds a write open and reads beside it, and fails with one connection. The same browsing: a feed's items at p95 10ms where it was 133, a search 22 where 119, the feed list 89 where 242. The load tests' SQLite budgets are tightened to match; the Rust tests take 2.8s where they took 7.5. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
55 lines
2.7 KiB
JavaScript
55 lines
2.7 KiB
JavaScript
import http from 'k6/http';
|
|
import { check, sleep } from 'k6';
|
|
import { BASE, FEEDS, ITEMS, as, me, pick, feedId, p95 } from './lib.js';
|
|
|
|
// An evening's browsing: twenty-five people at once opening their feed list, All Subscriptions,
|
|
// a feed, a search, the Directory and a feed's page in it. Each answer's budget is well above what
|
|
// it takes now, so it fails on a query that has started asking once per feed -- the Directory
|
|
// asked the database three questions a feed until 0.10.0 -- not on a slow minute. Fifty measured
|
|
// the queue for what was SQLite's one connection (#136) more than any query.
|
|
export const options = {
|
|
scenarios: {
|
|
evening: {
|
|
executor: 'ramping-vus',
|
|
stages: [{ duration: '15s', target: 25 }, { duration: '45s', target: 25 }, { duration: '10s', target: 0 }],
|
|
},
|
|
},
|
|
thresholds: {
|
|
http_req_failed: ['rate==0'],
|
|
checks: ['rate==1'],
|
|
// About twice each one's p95 on 2026-10-05 on Tower, and no less than 50ms, where a few ms
|
|
// either way is noise. SQLite: 89, 17, 10, 22, 112, 126ms; Postgres: 54, 34, 24, 44, 71, 88ms.
|
|
'http_req_duration{name:feeds}': p95(200, 150),
|
|
'http_req_duration{name:all-entries}': p95(50, 100),
|
|
'http_req_duration{name:feed-entries}': p95(50, 100),
|
|
'http_req_duration{name:search}': p95(60, 100),
|
|
'http_req_duration{name:directory}': p95(250, 200),
|
|
'http_req_duration{name:listed}': p95(300, 200),
|
|
},
|
|
};
|
|
|
|
export default function () {
|
|
const u = me();
|
|
const feeds = http.get(`${BASE}/api/feeds`, as(u, 'feeds'));
|
|
check(feeds, { 'your thirty feeds': r => r.status === 200 && r.json().length === 30 });
|
|
|
|
const all = http.get(`${BASE}/api/entries?limit=50&filter=all&sort=published&dir=desc`, as(u, 'all-entries'));
|
|
check(all, { 'All Subscriptions, a page of it': r => r.status === 200 && r.json().entries.length === 50 });
|
|
|
|
const f = pick(feeds.json());
|
|
const one = http.get(`${BASE}/api/feeds/${f.id}/entries?limit=50&sort=title&dir=asc`, as(u, 'feed-entries'));
|
|
check(one, { 'a feed of yours, every item': r => r.status === 200 && r.json().entries.length === ITEMS });
|
|
|
|
// Every generated item mentions the weather, in its text, not its title.
|
|
const found = http.get(`${BASE}/api/entries?q=weather&limit=50`, as(u, 'search'));
|
|
check(found, { 'a search of everything you read': r => r.status === 200 && r.json().total === 30 * ITEMS });
|
|
|
|
const dir = http.get(`${BASE}/api/directory`, as(u, 'directory'));
|
|
check(dir, { 'the whole Directory': r => r.status === 200 && r.json().length === FEEDS });
|
|
|
|
const listed = http.get(`${BASE}/api/directory/${feedId(Math.floor(Math.random() * FEEDS))}`, as(u, 'listed'));
|
|
check(listed, { "a feed's page in the Directory": r => r.status === 200 && r.json().items.length === ITEMS });
|
|
|
|
sleep(1 + Math.random() * 2);
|
|
}
|