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
Performance regression: v5 is 2–7× slower than v3.8.0 for local evaluation #198
Benchmarked flagsmith 5.0.1 vs 3.8.0 against the same environment (edge API, enable_local_evaluation=True, 262 features, single-threaded, after 200-iter warmup).
p50 per call
Operation
v3.8.0
v5.0.1
Regression
get_identity_flags
0.39 ms
0.82 ms
2.1×
get_environment_flags
0.11 ms
0.79 ms
7.4×
is_feature_enabled (cached Flags)
0.08 µs
0.08 µs
—
Throughput drops from ~2,570 → ~1,215 identity evals/sec per core. Latency variance also grew (stdev ~10 µs → ~220 µs).
We've released #200 to mitigate this, but we still need to address the issue described here. The rough plan is to profile the repro benchmark to find the exact bottleneck in evaluation. Keep in mind we need to add .all_flags() now.
Activity
perf: Speed up local-evaluation hot path for large environments
khvn26 commentedon Apr 29, 2026
We've released #200 to mitigate this, but we still need to address the issue described here. The rough plan is to profile the repro benchmark to find the exact bottleneck in evaluation. Keep in mind we need to add
.all_flags()now.