feat: JFR events for open, HTTP range, segment decode/encode, chunk filtering and writer back-pressure
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 55/100
- Tipo de issue
- Funcionalidade
- Clareza
- Claramente especificada
- Status de atividade
- Ativa
- Stack de tecnologia
- java
- Domínio
- backend, observability
Direção de pesquisa
Start by reading the reader and writer entry points named in the issue: VortexReader.open, VortexHttpReader.open, SerializedArrayDecoder.decode, ScanIterator, and VortexWriter. Add the JFR event classes and wire them into those paths as specified, then use the named tests to check event fields, filtering counts, and back-pressure duration. Done when the event tests pass and the reference guide, how-to guide, changelog, and module map are updated.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Goal
Emit JDK Flight Recorder events from the reader and writer, so a JFR recording shows where a read or write spends its time (file open/mapping, HTTP range fetches, per-segment decode/encode, chunk pruning, writer back-pressure) with no extra dependency and near-zero cost when recording is off.
Events
New package core/src/main/java/io/github/dfa1/vortex/core/jfr/ (with package-info.java). Each event is a public class extending jdk.jfr.Event, annotated @Name("io.github.dfa1.vortex.X"), @Label, @Category({"Vortex", …}), @Description and @StackTrace(false). Public fields get /// docs (doclint is all); byte sizes get @DataAmount.
| Class | Category | Fields |
|---|---|---|
FileOpenedEvent |
I/O | source, fileSize, formatVersion, segmentCount |
FileMappingEvent |
I/O | file, size |
HttpRangeEvent |
I/O | source, offset (-1 = tail), length, status (0 = no response) |
SegmentDecodedEvent |
Decode | encoding, rowCount, segmentSize |
ChunkFilterEvent |
Filter | totalChunks, chunksPruned, chunksWithoutMatch, chunksReturned, rowsReturned |
SegmentEncodedEvent |
Encode | encoding, bufferCount, encodedSize |
SegmentWaitEvent |
Pipeline | segmentsInFlight |
Reader wiring
Pattern: event.begin(), set fields, commit().
VortexReader.open(path, registry, layoutRegistry):FileOpenedspans the whole open and is committed after parse;FileMappingwrapschannel.map. A failed open emits noFileOpened.VortexHttpReader.open(uri, registry, layoutRegistry, client):FileOpenedbegins beforefetchTailand is committed after the reader is built.- New private
sendRange(req, client, uri, offset, length)wrapsclient.sendin try/finally and always commitsHttpRange, withstatus = 0on failure.fetchTailcalls it with offset-1andTAIL_SIZE.bytes();fetchRangewithfromandto - from + 1. - New package-private
static String describe(URI)returningscheme://host[:port]+ raw path. It drops user info, query and fragment, because presigned URLs carry credentials. Used for everysourcefield.
- New private
SerializedArrayDecoder.decode: begin at the top; afterregistry.decode(ctx)setencoding = node.encodingId().id(),rowCount,segmentSize = segLen, then commit. Covers both readers.ScanIterator:- New counters
chunksPruned,chunksWithoutMatch,chunksReturned. - In
hasNext(), splitcanPruneChunk(...) || !selectMatchingRows(...)into two branches that each count,chunkIndex++; continue. - Increment
chunksReturnedinnext(). close()callsemitChunkFilterEvent(), a no-op whenfilter == null || chunks == null.
- New counters
Writer wiring (VortexWriter)
encodeSegment: begin at the top; before returning,if (event.shouldCommit())fillencodingfromresult.rootNode().encodingId().id(),bufferCount,encodedSize, then commit. Failures emit nothing.drainSegments: replacepending.poll().join()with a staticawaitHead(head, pending.size() + 1). It joins directly ifhead.isDone(); otherwise begins aSegmentWaitEvent, joins in atry, commits in thefinally.- No change to the writer's default behavior. (The default executor runs tasks on the caller, so
SegmentWaitnever appears there.)
Tests
Given/When/Then throughout. For events committed on other threads, assert presence and field values, never exact counts.
core/src/test/.../core/testing/JfrRecorderTest.java: abstract base; aRecordingStreamwithsetReuse(false)starts in@BeforeEach; offersawaitEvents()andevents(name).- reader
VortexReaderJfrTest(fixtureprimitives.vortex):FileOpenedandFileMappingfields; a too-small file emits noFileOpened. - reader
VortexHttpReaderJfrTest(mockedHttpClient): tailHttpRange(offset -1, status 206);sourcehas no credentials or query; status 0 whensendthrowsIOException. - writer
JfrEventsTest(usesLegacyZoneMaps.OPTIONS, same package):SegmentEncodedpresent with non-negative sizes (avortex.sequencesegment has 0 buffers).- Default executor: no
SegmentWait. - Executor sleeping 200 ms before each task:
SegmentWaitduration > 50 ms andsegmentsInFlight> 0. - Chunks 1..50, 51..100, 101..150 with
eq(id, 75)→ totals 3/2/0/1 and 1 row. - Single chunk {1, 100} with
eq(id, 50)→ 1/0/1/0 and 0 rows. - Unfiltered scan emits no
ChunkFilter.
Docs (same commit)
docs/reference.md: "JFR events" section (event table) + TOC entry.docs/how-to.md: "Find where a read or write spends its time (JFR)".CHANGELOG.md:## [Unreleased]→ Added.AGENTS.md:core.jfrline in the module map.
Verify
./mvnw test -pl core,reader,writer -am./mvnw verify -DskipTests(Javadoc lint + checkstyle)
- Linguagem predominante
- Java
- Estrelas
- 3
- Forks
- 2
- Merge médio
- 9h 47min
- PRs com merge (30d)
- 128
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de dfa1/vortex-java
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 66/100
dfa1/vortex-java#636 ·
Mantenedores costumam responder em até 1 dia
-
bug
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 70/100
dfa1/vortex-java#655 ·
Mantenedores costumam responder em até 1 dia
-
perf
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 30/100
dfa1/vortex-java#651 ·
Mantenedores costumam responder em até 1 dia
-
Writer: string columns written as per-chunk dicts where Rust uses its dict layout (up to 2x larger)Abertaperf
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 30/100
dfa1/vortex-java#650 ·
Mantenedores costumam responder em até 1 dia
-
perf
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 28/100
dfa1/vortex-java#649 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de dfa1/vortex-java
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 66/100
a2aproject/a2a-java#1275 ·
Mantenedores costumam responder em até 1 dia
-
module/ftp Type/Bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
ballerina-platform/ballerina-library#9476 ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
anwilli5/coin-collection-android-US#515 ·
Mantenedores costumam responder em até 1 dia
-
status: waiting-for-triage type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
spring-projects/spring-integration#11654 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 Menos de uma hora Facilidade para iniciantes 70/100
Vakore/ZappierGames#248 ·