Skip to content

fix: restore write encoding perf by encoding vectors before transform walk - #265

Closed
rkruze wants to merge 1 commit into
mainfrom
roko/write-vector-encoding-perf
Closed

rkruze wants to merge 1 commit into
mainfrom
roko/write-vector-encoding-perf

Conversation

@rkruze

@rkruze rkruze commented Sep 23, 2026

Copy link
Copy Markdown
Member

#259 moved vector base64 encoding into a second pass after _turbopuffer_transform. The walk then went into every vector and made one Python call per float, only for the result to be base64-encoded right after. For 1000 rows x 1536 dims, transform time went from ~8ms (2.8.0) to ~105ms (2.9.0+).

@rkruze
rkruze requested a review from benesch September 23, 2026 03:58
@rkruze rkruze changed the title fix: don't base64-encode vector arrays fix: restore write encoding perf by encoding vectors before transform walk Sep 23, 2026
@rkruze rkruze closed this Sep 23, 2026
@rkruze
rkruze deleted the roko/write-vector-encoding-perf branch September 23, 2026 03:59
@rkruze
rkruze restored the roko/write-vector-encoding-perf branch September 23, 2026 03:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant