op: schema-extend

5 events · 870.00 us wall · 738.30 us DB (85%) · 131.70 us non-DB (15%)

DB 738.30 usnon-DB 131.70 us

Transactions

Autocommit mode — every statement was its own transaction. Group related writes in one explicit transaction (and reads outside it) to cut round-trips.

#	duration	writes	max idle	outcome	longest template
1	150.30 us	1	—	autocommit	`MERGE INTO SETTINGS (K, V) KEY(K) VALUES (?, ?)`
2	53.50 us	1	—	autocommit	`MERGE INTO SETTINGS (K, V) KEY(K) VALUES (?, ?)`
3	54.60 us	1	—	autocommit	`MERGE INTO SETTINGS (K, V) KEY(K) VALUES (?, ?)`

Timeline

gap is idle time since the previous event on the same thread — highlighted rows had noticeably more app/non-DB time before them than the rest. Follow those to find where the op lost its wall-clock time outside the database.

+offset	gap	event	duration	template	params	call-site
0 ns	—	PREPARE	479.60 us	`MERGE INTO SETTINGS (K, V) KEY(K) VALUES (?, ?)`	—	`fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66`
531.80 us	52.20 us	EXECUTE_UPDATE	150.30 us	`MERGE INTO SETTINGS (K, V) KEY(K) VALUES (?, ?)`	`[1] currency_label_EUR, [2] Euro`	`fi.vesas.jdbclens.sample.cobol.CodeLookupService.seedCodes:33`
713.50 us	31.40 us	EXECUTE_UPDATE	53.50 us	`MERGE INTO SETTINGS (K, V) KEY(K) VALUES (?, ?)`	`[1] status_label_OPEN, [2] Open`	`fi.vesas.jdbclens.sample.cobol.CodeLookupService.seedCodes:35`
792.60 us	25.60 us	EXECUTE_UPDATE	54.60 us	`MERGE INTO SETTINGS (K, V) KEY(K) VALUES (?, ?)`	`[1] shipping_label_STD, [2] Standard`	`fi.vesas.jdbclens.sample.cobol.CodeLookupService.seedCodes:37`
869.70 us	22.50 us	CLOSE	300 ns	—	—	`stack[-1]`