---
title: "Comment by Kartik N V J K on \"Late Chunking + Jina v4: Context-Aware Embeddings, Self-Hosted on GCP\" | Hashnode"
description: "The late-chunking flip is the part I keep coming back to, embedding first and cutting after preserves neighbor context that vanilla chunk-then-embed silently dr"
url: "https://hashnode.com/posts/late-chunking-jina-v4-context-aware-embeddings-self-hosted-on-gcp/6a8d507e6234228829f0b857/comment/6a8dfc085dca1240fc336c27"
---

[Discussion](https://hashnode.com/posts/late-chunking-jina-v4-context-aware-embeddings-self-hosted-on-gcp/6a8d507e6234228829f0b857)

Comment [Late Chunking + Jina v4: Context-Aware Embeddings, Self-Hosted on GCP](https://hashnode.com/posts/late-chunking-jina-v4-context-aware-embeddings-self-hosted-on-gcp/6a8d507e6234228829f0b857)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Aug 25](https://hashnode.com/posts/late-chunking-jina-v4-context-aware-embeddings-self-hosted-on-gcp/6a8d507e6234228829f0b857/comment/6a8dfc085dca1240fc336c27)

The late-chunking flip is the part I keep coming back to, embedding first and cutting after preserves neighbor context that vanilla chunk-then-embed silently drops. I also like that you kept the latency numbers honest (0.14 to 0.8s per chunk on self-hosted GCP vs 1 to 3s on Spaces), the "always-on cost" caveat is what most write-ups skip. Curious whether you saw retrieval quality shift on tables and code blocks specifically, those tend to break mean-pooled token embeddings for us.