Accepting submissions
Not accepting submissions
Submission guidance
When submitting, please tell us:
- What problem your session addresses
- Who the session is for
- What the audience will learn
- Whether the work is in production, experimental, or in progress
- What technical details, demo, case study, or story you will share
- What makes the session useful to practitioners
Please also add tags to help us understand your proposal. Tags may describe domains, techniques, systems, or formats, for example:
#observability #inference #agents #security #governance #finops #sre #devops #platformengineering #mlops #databases #scalability #kubernetes #developerplatforms #failurestory #demo #workshop #casestudy #workinprogress
|
SS
Swapnil Prakash Sankla [WIP] One Dataset, Three Physical Representations (YOUR SCHEMA decides how much work the query engine does at runtime)Session title One Dataset, Three Physical Representations more
I am submitting: To speak
I have a submission for: A talk - 30-40 mins
|
|
AS
Aditya Singh [Add a catchy title or a Work-in-Progress (WIP) title]Rootconf 2026 Proposal Draft Session title When the Client Disconnects but the Agent Keeps Running more
I am submitting: To speak
I have a submission for: A talk - 30-40 mins
|
|
VK
Vivek Kalyanarangan Decoding at a million tokens when the KV cache lives in host memory: what actually bounds the stepDecoding at a million tokens when the KV cache lives in host memory: what actually bounds the step more
I am submitting: To speak
I have a submission for: A talk - 30-40 mins
|