Edge Functions: fresh workers on sequential requests
The user is experiencing unexpected behavior with Supabase Edge Functions where fresh workers are frequently created for sequential requests in production, despite expected reuse. They are seeking clarification on whether this behavior is normal and how it affects performance optimizations like in-memory caching and pooled connections.