op: seed-customers

4 events · 32.86 ms wall · 14.22 ms DB (43%) · 18.64 ms non-DB (57%)

DB 14.22 msnon-DB 18.64 ms

Transactions

#	duration	reads	writes	max idle	outcome	longest template
1	32.72 ms	0	1	18.34 ms	commit	`INSERT INTO customers (id, name, email, phone, address_line, city, state, postal_code, country, timezone) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?…`
2	5.40 us	0	0	0 ns	commit	—

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	1.46 ms	`INSERT INTO customers (id, name, email, phone, address_line, city, state, postal_code, country, timezone) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?…`	—	`fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66`
19.80 ms	18.34 ms	EXECUTE_BATCH	11.93 ms	`INSERT INTO customers (id, name, email, phone, address_line, city, state, postal_code, country, timezone) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?…`	—	`fi.vesas.jdbclens.capture.CapturingPreparedStatement.executeBatch:301`
31.90 ms	170.00 us	COMMIT	822.40 us	—	—	`fi.vesas.jdbclens.capture.CapturingConnection.commit:202`
32.85 ms	130.50 us	CLOSE	5.40 us	—	—	`stack[-1]`