Importing bulk imports keeps timing out.

[KaricAllegra]

So, I brought this issue up before, but got no help. So, I'm hoping someone else sees this and can at least let me know if anything similar is going on that they've noticed.

TLDR: Could the new Netbox recommendation for using Modules be causing me not to be able to bulk import?

Upgraded to 4.6.0 and am attempting to import one Telcomm room at a time (<50 devices). It keeps timing out. I have updated all the config settings I know how to: assigning the right number of workers for my core and updating the web pages to timeout after 10 minutes, and still not enough.

I have done other buildings with LARGER bulk imports before, and I have never had a problem. The differences between then and now are the version, and now, for this building, I am attempting to use the Netbox-recommended way of modeling everything with modules.

This building is the first time all my Corning fiber housings are now modeled as a device with 48 module bays, and then each module can have a Corning cassette added. All my fiber switches are now also devices with 49 module bays. We used to use Inventory, but for this building, I decided to go with Netbox's recommendation to use the Module bay way.

Understand, I'm more of a web user than a Linux user. So, I used AI, and it suggested there's an issue with how Postgres indexes the new modules. There were a bunch of commands it had me run (htop, Postgres stuff, log file watches, etc) again, over my head... but it did keep coming back to Postgres trying to index all the new module bay database entries.

So, is there anyone else out there that has started doing this, and are you seeing anything similar?

[KaricAllegra]

This issue seems to have been fixed by #22146

So if you are seeing this performance hit, upgrade to at least v4.6.1