9

V 12.1.1, starting a kernel, e.g. by entering wolframscript in the shell, takes an unexpectedly long time (~5 min, the time elapsed between pressing Enter and the showing-up of In[1] := ); but the same operation for V 12.0 takes merely ~3 sec.

I wonder if I am the only one experiencing this.


Update

Also, inspired by @Ordinaryusers68 's answer, I find these two posts:

where, an option -nopaclet is mentioned when starting the kernel.

  • 2
    Thanks so much for bringing this up! I have similar problems since Mma 12.0, but I was to lazy to debug them properly. BTW, in my case this happens even when the system has a proper internet connection. For me PacletManager$AllowInternet = False' works best. I guess I'll put this into my init.m and update the paclets from time to time by hand. – vsht Jul 20 '20 at 18:55
  • Hi, @vsht , thx for your information. Actually, I had hesitated for a quite long time before I decided to put this post up. And I am really happy if it can help anyone. :) – Αλέξανδρος Ζεγγ Jul 21 '20 at 02:01

1 Answers1

6

I don’t know if the problem you encountered is the same as the problem described in this post. If the same, you need to disable automatic updates.

This failure is caused by the paclet update system. Just turn off this automatic update. The easiest way to close the update is to delete the "PacletSiteData_10.pmd2" file.