You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature Request: SuperCompress context compression for real-time AI pipelines #254
Feature: Compress LLM Context in Pathway Pipelines
Problem: Pathway processes real-time data streams through LLM calls. Each window of streaming data sent to the LLM consumes tokens — compressing it before processing would reduce costs for streaming AI workloads.
Proposed Solution: Provide a SuperCompress integration example for Pathway's LLM processing.
fromsupercompressimportCompressorimportpathwayaspwcompressor=Compressor()
# In a Pathway LLM processing pipelinedefcompress_and_process(data, query):
compressed=compressor.compress(data, query)
returnllm_process(compressed)
Hi! I'd be interested in working on this, but before writing any code I'd like to check a few things with the maintainers, in line with CONTRIBUTING.md.
Is an integration like this something the project wants? Would it be a better fit as a docs/example page, a small optional component in the LLM xpack, or something that belongs outside this repo (e.g. llm-app)?
If it is an example or optional component, I would keep supercompress an optional, lazily imported dependency, with no change to core dependencies. Is that acceptable?
@arjunkshah, could you share a bit more about the use case? In particular: which Pathway pipelines you've applied this to (streaming windows, RAG context, something else), what the real Compressor API looks like (the snippet in the description looks like pseudocode), and the license, supported Python versions and maintenance status of the package. It would also help to see how the ~65% compression / 100% recall figures were measured and on what data, since I'd want to reproduce them before describing them in any docs.
If a maintainer gives the go-ahead and a preferred shape, I'll open a small, self-contained PR with tests and a CHANGELOG entry, plus a short account of how it was built. Happy to drop it if this isn't a direction you'd like to take.
Activity
Shiv-61 commentedon Oct 17, 2026
Hi! I'd be interested in working on this, but before writing any code I'd like to check a few things with the maintainers, in line with CONTRIBUTING.md.
supercompressan optional, lazily imported dependency, with no change to core dependencies. Is that acceptable?CompressorAPI looks like (the snippet in the description looks like pseudocode), and the license, supported Python versions and maintenance status of the package. It would also help to see how the ~65% compression / 100% recall figures were measured and on what data, since I'd want to reproduce them before describing them in any docs.If a maintainer gives the go-ahead and a preferred shape, I'll open a small, self-contained PR with tests and a CHANGELOG entry, plus a short account of how it was built. Happy to drop it if this isn't a direction you'd like to take.
Thanks!