Jul797 Upd Online

If you have not yet applied the , schedule a maintenance window this week. For those already running it, monitor your logs for the JUL-4xx warnings and apply the workarounds above.

| Metric | Pre-Update (v.796) | Post-Update (jul797 upd) | Change | |--------|--------------------|---------------------------|--------| | API response time (p95) | 342 ms | 211 ms | | | Memory footprint (idle) | 1.2 GB | 890 MB | -26% | | Cold start time | 8.4 sec | 5.1 sec | -39% | | Throughput (req/sec) | 4,200 | 6,750 | +61% | jul797 upd

A: Approximately 4–7 minutes on SSD storage. HDD-based systems may take up to 20 minutes. If you have not yet applied the ,

| Issue ID | Description | Workaround | |----------|-------------|-------------| | JUL-421 | GUI dashboard fails to refresh on Firefox 135+ | Clear cache or use Chromium-based browser | | JUL-422 | High CPU usage when --sync-parallel exceeds 12 threads | Cap threads at 8 using --max-threads 8 | | JUL-423 | Incompatibility with Python 3.13’s new GIL mode | Run in legacy mode: export JUL797_LEGACY_GIL=1 | We tested the update on a standard AWS c6a.2xlarge instance (8 vCPU, 32 GB RAM). The metrics below represent an average of 50 runs: HDD-based systems may take up to 20 minutes

After months of beta testing and community feedback, the official has been rolled out globally. This is not merely a cosmetic refresh; it is a fundamental architecture shift designed to address memory leaks identified in the previous Q1 release, patch three zero-day vulnerabilities, and improve cross-platform interoperability.

✅ Recommended for all production environments. Test on staging first if you use Python 3.13 or custom TLS implementations. Stay tuned for the next patch: "aug881 upd" – expected Q3 2026, focusing on distributed tracing and WebAssembly plugins.