RepoJournal
Google

Google

JAX, the GenAI SDK, and the Cloud libs — Google's open source layer

Pick a date

  1. Sun 3 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Sun 10 may
  9. Mon 11 may
  10. Tue 12 may
  11. Wed 13 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Mon 18 may
  16. Tue 19 may
  17. Wed 20 may
  18. Thu 21 may
  19. Sat 23 may
  20. Sun 24 may
  21. Mon 25 may
  22. Tue 26 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

JAX CLEANS HOUSE WITH PROFILER HOOKS AND PERFORMANCE FIXES

By RepoJournal · Filed · About Google

JAX shipped a flurry of optimizations and rollbacks overnight, addressing profiling bottlenecks and reverting experimental changes that didn't land.

The profiler got subprocess registration hooks [1] to track work across process boundaries—critical for distributed training debugging. Meanwhile, the team reverted two experimental features that weren't ready: a versioning fix [2] and a Pallas matmul fusion change [4], both less than 24 hours old. The real win is performance: JAX stopped using nanobind for Doc object construction [3], eliminating hash table overhead that was tanking jaxpr printing speed on large models. On the Cloud Python side, documentation generation is getting untangled—Bigtable docs are closer to working again after fixing librarian regex patterns [6], and the release pipeline is tightening its exclusion rules [5]. BigFrames is still in refactoring mode, isolating integration tests into separate projects [7] to prevent crosstalk.

Action items

References

  1. [1] Add subprocess registration hooks to JAX profiler libraries. ↗ google/jax
  2. [2] Fix forward with versioning. ↗ google/jax
  3. [3] Don't use nanobind to construct Doc objects. ↗ google/jax
  4. [4] Roll back the Pallas change ↗ google/jax
  5. [5] chore: expand release exclusion lists ↗ googleapis/google-cloud-python
  6. [6] chore: fix Bigtable integration replacements (#16915) googleapis/google-cloud-python
  7. [7] test: Use seperate test projects for bigframes integration tests (#16900) googleapis/google-cloud-python

FAQ

What changed in Google on May 2, 2026?
JAX shipped a flurry of optimizations and rollbacks overnight, addressing profiling bottlenecks and reverting experimental changes that didn't land.
What should Google teams do about it?
Update JAX if you're profiling distributed workloads—subprocess hooks are shipping now • Monitor the Pallas matmul fusion flag if you rely on einsum performance tuning • Watch google-cloud-python for Bigtable docs re-enablement in the next cycle
Which Google repositories shipped on May 2, 2026?
google/jax, googleapis/google-cloud-python

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.