The image for 6.0.0 with ADDONS takes forever to boot #105
Comments
|
Maybe there are no Py 3.11/arm64 wheels released for some dependencies and it needs to compile them? Just guessing, w/o logs difficult to tell. |
|
@jensens Can you try the commands above, and see if you can reproduce it? The logs: |
|
wrapt is the only new dependency with the need of a build, is this what take so long? probably it would be good to create an issue here https://github.com/GrahamDumpleton/wrapt/issues and ask if we can have 3.11 wheel too. |
The new build method with |
|
First we need to try if it helps. @mauritsvanrees would this be possible? |
|
@jensens I don't understand what you are proposing. For me, So it takes 3 seconds to install |
|
@sneridagh I wanted to try out your two initial commands, but the first one with rc1 already lets me stare maybe ten minutes at this output, waiting for something to happen: |
|
@mauritsvanrees no idea why, is it ARM64 related? I do not propose anything. Before, I want to know the problem. Seems something is slow in a specific combination. Work for me too, btw. Nothing is slow here. |
|
I have a Mac Intel, so no ARM. With rc1 I was waiting for a long time, but actually it was ready, it just did not tell me. I waited an hour and then pressed CTRL-C and I got the output that should have been printed an hour ago: Trying it again, I can visit http://localhost:55001/plone just fine... :-D With 6.0.0 it is the same, quite fast. |
|
@sneridagh sounds odd, any idea how to reproduce? |
|
For the robot server this is ok, so when it shows: it's ready and you can access to http://localhost:55001/plone. Reaching there for me it's like I said, 45s vs 8s before final. If you could try both commands, then time them: Running rc1: Running 6.0.0 final: Would be great. |
|
Problem is that I do not see when it is ready. The last output is this on rc1: On 6.0.0 the above warning notice is not there, so this is the last I see: I only get more text when I press CTRL-C. This will retry the page until it gets a result.
But maybe you should not specify beta versions for the add-ons: Plone already pins them. Let's try this: In the last call, when I ignore lines with "Requirement already satisfied", this is the output: That is 24 packages downloaded. I suspect the speed difference comes from either pip or setuptools. |
|
Just taking a look at CI (GHA) and the performance is as bad as locally... I really think we should take a closer look and make the required tests using other versions (even downgrade). |
|
I don't know if it's related, but we just updated our setup to Plone 6.0.0 and noticed significantly longer build times when using the versions for pip, setuptools, wheel and zc.buildout from dist.plone.org.
|
narrowed it down:
|
|
What can help a lot, if you have a buildout download cache, is to delete (or temporarily rename) this, especially the But the exact setuptools version should not matter too much for this part I think, except that setuptools 67 is extremely slow here. I have a PR for that, which seems close to being merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In comparison with the previous images:
Running rc1:
Running 6.0.0 final:
For me, M1Max first command runs in 8s, the latter in 47s... No clue why, it seems that pip takes much more "Requirement already satisfied:" checks than before.
/cc @jensens @ericof we did update pip to latest and Python 3.11, right? Any idea if that could be the reason?
The text was updated successfully, but these errors were encountered: