The v3.4 to v4 migration codemod is unusably slow

[umstek]

Description

I have a react project with webpack which is a bit old. However, ai worked without an issue. The only features I'm using are:

experimental_useObject

useCompletion

and there's likely nothing to migrate. But still it takes hours. I waited 4 hours when my machine crashed due to an unrelated issue.

Code example

import { experimental_useObject as useObject } from 'ai/react';

import { useCompletion } from 'ai/react';

AI provider

@ai-sdk/google v1.0.0 (in backend, so unrelated?)

Additional context

Linux 6.8.0-48-generic/Linux 6.8.0-48-generic

[lgrammel]

If you only use those functions, there is likely nothing to migrate. Can you just try using 4.0 without running the migration?

One thing you may want to change manually is removing the await from streamText / streamObject

[umstek]

Migration worked for the backend. Everything seems fine so far.

[wong2]

Yes, it's reallly slow

[shaper]

Hi there, thanks for the report and sorry to hear the performance isn't good for your code base. A few things that could help us look into this if you can share:

• rough scale of codebase size (e.g. XXX KLOC)
• what kind of machine you're running on (e.g. rough year of Mac laptop, Linux server w/ N cores, ...)
• cpu load on machine (via top, w, Activity Monitor, etc.)

[umstek]

@shaper
less than 100KLOC
Ubuntu 24.04 on Core i7-8565U, 16GB RAM (Thinkpad)
I didn't notice any CPU usage due to the codemod running, typically was around 30-40%

[shaper]

@shaper less than 100KLOC Ubuntu 24.04 on Core i7-8565U, 16GB RAM (Thinkpad) I didn't notice any CPU usage due to the codemod running, typically was around 30-40%

Thank you. Do you know whether all of the code was already local, or if some was potentially loading over a network mount?

We have several potential performance improvements in mind and your feedback can help guide what order we approach them in.

[umstek]

Code was local.

It has ~500 stale branches and 3000 commits.