-
### Description
Hi,
we found a changed behaviour in IP 3.4.1 compared to the IP 2.x implementation.
We are using IP to execute python code in multiple threads.
To improve performance the work th…
-
**Is your feature request related to a problem? Please describe.**
When executing a full build the tests in `engine` consume the most time. Sometimes I just want to skip those, but want to run other …
-
### Describe the feature
We re-execute a block in our engine interceptor that simulates reorgs, but this does not currently support execution requests, which were introduced in Prague.
https://git…
-
We should instrument the GPU physical execution engine so that it is compatible with the built-in Polars [LazyFrame profiler](https://docs.pola.rs/py-polars/html/reference/lazyframe/api/polars.LazyFra…
-
Aim to remove panicking code from production codebase. If possible, just remove or replace with Result. If better to leave in place, add a comment explaining why
-
## Road to vectorized/hybrid execution
Writing this down, mostly to sort out my thoughts, but also to share this for some further discussion.
## Current state
Execution of queries in CrateD…
-
https://github.com/thanos-io/promql-engine/pull/452 supports tracking peak samples during an execution of the query.
What we are still missing from the old Promql engine is max samples limit enforc…
-
The Platform should provide an extensible mechanism (`ServiceLoader`?) so that user code can create "closeable resources" that are injected as part of the context received by `TestEngine` implementati…
-
Currently, Tailcall supports two execution engines:
1. **Async GraphQL Engine**: Works out of the box and can be enabled using `enableJIT: false`.
2. **JIT Engine (default)**: A faster alternative…
-
The current implementation has some issues/miss implementations that degrade system performance for larger/more complex logic.
Known issues
- [x] **execution stack traces**: since they blindly a…