​​The Cambridge Crystallographic Data Centre (CCDC).
The CCDC websites use cookies. By continuing to browse the site you are agreeing to our use of cookies. For more details about cookies and how to manage them, see our  cookie policy.

Why is WebCSD always slow at the beginning of each session?

Solution

Note: The following information applies only to WebCSD version 1 (legacy WebCSD).

Before a Java application can run, the "Java Runtime Environment" (JRE) must be initialised. This can take quite a few seconds (depending purely on the speed of your client machine and the version of Java you are using). Until the JRE has completely initialised, the page you are trying to use will be inactive and will probably appear empty.

Once the JRE has loaded the page will come to life, the missing components will appear, and you will be able to use WebCSD. The JRE only needs to initialise once per browser session, the first time a Java application is run. The next time Java is used, the application should appear virtually immediately due to the internal caching that automatically takes place within the JRE.​