I seem to remember that some part of poetry's slowness is due to how the python index works and is therefore a problem shared by all such tools.

That said, I've used both pipenv and poetry, and I had projects where pipenv would simply time out when trying to resolve packages. I haven't seen the same behaviour with poetry (indeed, that was the reason I migrated one project from pipenv to poetry after I just had to give up with the former).