I am not sure if it is my connection or just the server busy, but it takes a while to get a response. Once it starts downloading, speeds seems normal though…
Yes, I noticed that too. I wonder if with the new versioning scheme the query is returning more matches or something like that.
I’m seeing 0.5 second response to a hard reload of https://download.slicer.org, loading 130KB. There’s no dynamic query happening; the server is generating the HTML from a local sqlite db. Midas queries happen separately on the backend and only every few hours or so.
If the extension catalog is also slow, then its probably something else, since download.slicer.org and the extension manager don’t use any shared front-end.
—Mike
1 Like
Thanks Mike.
For me it was the extension manager taking a while to come up.
Looking at the network performance associated with page like this one (loaded in the extension manager):
with cached assets (similar time after discarding the cache) is ~2s
Yes, that site comes up quickly for me. I think the issue was opening the extension manager window after a fresh install. Is anyone else seeing that?
Slow startup of extension manager on Mac is most likely due to that the executables are not signed. You can easily self-sign the application to see if it fixes the issue. See details here: https://github.com/Slicer/Slicer/issues/4724
Is only the first loading is slow, or reloads are slow, too?
Does the app store page load slowly in a regular Chrome browser, too?
Yes, that is very slow. The page comes up but the wait animation “Loading extensions” is up for several minutes so far.
Looking at the networking tab of the chrome developer tools it says the list extensions request is pending (the form data looks right).
Interestingly the app store link I included above loaded in a few seconds at that time (40 minutes ago), but now it has been loading for several minutes and extensions still haven’t showed up. Probably it’s just the usual unpredictability of the ancient Midas server.
Yesterday morning I had poor response when trying to download the Windows Slicer Preview from I believe both the cdash uploaded package URL and the link from download.slicer.org which is something like https://download.slicer.org/bitstream/1222761. If these requests are both served by the Midas server then I would think that is the culprit.
Yes, it took 8.9 minutes to load in one of my tests. Other times it’s nearly instant.
https://download.slicer.org/bitstream/1222761 is literally a redirect to Midas. download.slicer.org never handles the bits.
The redirect is instantaneous.
—Mike
download.slicer.org page is very fast and reliable - thank you Mike! Sometimes the package download takes a few minutes instead of a few ten seconds, but that’s still fine.
The problem is with the extension download page (http://slicer.kitware.com/midas3/slicerappstore). Right now, the page with specified revision usually loads within seconds, page without revision usually loads within a minute. However, sometimes loading takes several minutes or more (or times out).
What might be a recent regression is that http://slicer.kitware.com/midas3/slicerappstore takes a really long time to load (but when we specify a revision then the page loads within seconds). @jcfr could the few very high revision numbers that showed up this week affect the latest revision detection mechanism of the page?
While I removed the offending packages, I will remote connect to the database and manually inspect the tables.
Just wanted to report that upon trying to download the Slicer preview from the main download page today at 3:12 pm EST, that it got stuck with “Waiting for slicer.kitware.com…” for a long time. I ended up reloading the webpage and trying again and actually recording the time it would take to begin serving the download. It took 1 min 45 seconds to actually begin downloading. This was on my home internet which is stable and once it started downloading the ~200MB package it finished in like 4 seconds because of my download speeds. Faster response to begin serving the download would be greatly appreciated.
1 Like
Thanks for reporting this. It is an open issue - see here - I’ve added your comment to it.
1 Like