[BUG] Faraday logging bodies is memory intensive when passing a large PDF

[taylars]

Basic checks

• I searched existing issues - this hasn't been reported
• I can reproduce this consistently
• This is a RubyLLM bug, not my application code

What's broken?

When passing in a large PDF, faraday and pretty print use a significant amount of memory for logging. When running a memory profile, you can see below that faraday and pp use 66MB of memory:

allocated memory by gem (bytes)
-----------------------------------
  33451488  pp-0.6.3
  33414027  faraday-2.14.0

However, if I disable body logging for faraday, that drops to a negligible amount:

allocated memory by gem (bytes)
-----------------------------------
   113466  faraday-2.14.0
        1176  pp-0.6.3

How to reproduce

1. Create an ActiveStorage object for a large PDF
2. Call OpenAI with that PDF

Expected behavior

This logging should not take such a large amount of memory.

What actually happened

Logging uses a significant amount of memory (over 10x the size of the PDF)

Environment

• Ruby version: 3.4.2
• RubyLLM version: 1.9.1
• Provider: OpenAI

[crmne]

You need to enable debug logging in order to log bodies and body visibility is the main value of debug logs here.

Were you reproducing high memory usage with debug logging off?

[crmne]

I fixed a separate but related issue by converting eager logger.debug "..." interpolation to lazy block logging logger.debug { "..." } which avoids large string allocations when debug is disabled. 90b8dd1

[taylars]

Ah interesting, I'll see if that helps - but yes, even if I set config.log_level = :info for both Rails and RubyLLM the issue still shows up

[crmne]

Can you try from RubyLLM's main branch?

[taylars]

Sorry for the delay here, but thanks for resolving this! I confirmed the fix works for me