I'm facing a severe performance degradation of performance in 9.0.5

[cperezabo]

The same code (a simple loop that executes a few hundred save!) that runs in 2s with 9.0.4 takes more than 30s with 9.0.5.
I just switch versions in bundle, re run and performance goes to hell!
I had also updated Ruby to 3.4.1 and thought that could have been that but, after downgrading Ruby to the previous version, the issue was still there.

Update 1:
Ok, I started testing my code with every mongoid commit after the v9.0.4 tag and the issue was introduced in 86f49a5

Update 2:
I've installed 9.0.5 again, edited the gem by reverting just the change introduced in 86f49a5 and everything performs fine as always. So there it is the problem!

[comandeo-mongo]

Hi @cperezabo , thank you for raising the issue! We are sorry that you are experiencing problems with Mongoid, we'll take a look into it. I created JIRA ticket to track the work - https://jira.mongodb.org/browse/MONGOID-5848

[cperezabo]

@comandeo-mongo, I can't create a Celda without a Rack, so why would I disable the validation that ensures that?.
As I said in my first comment, the issue was introduced in 86f49a5

[cperezabo]

Turning belongs_to_required_by_default off is not an option. Why would I disable a validation that was working before the update just to improve a performance issue introduced in the mentioned change?

[johnnyshields]

Fun times when a tiny version upgrade crushes your performance! Mongoid team > this is not acceptable and must be rolled back. You can consider re-introducing in a major version!

[cperezabo]

People don't even know how semantic versioning works. It's so cheap to be a developer.

[lucasDechenier]

Hi @cperezabo , thanks a lot for investigating and pinpointing the performance regression. I'm currently on Mongoid 9.0.6 and facing the exact same performance issue you described.

I'm considering locking the version at 9.0.4 for now — have you noticed any other issues or regressions in 9.0.4 that I should be aware of?

[lucasDechenier]

I have the same problem, any solution?