Hi,
I recently installed cryosparc v.4.6.2 on my new gpu servers.
Everything is working fine, except that when I open cryosparc in the beginning, it takes about 5-10 min until the projects/workspaces load. After this initial setback, the program works fine and fast, and subsequent jobs load quickly.
Does anybody know why it takes so long for cryosparc to load? This is obviously very inconvenient when I just want to quickly check the status of a job.
Thanks!
I have noticed the same on chrome for Mac, and typically a restart of chrome can circumvent the issue (though often this is not a desirable path). 4.6.0
Thanks @shifral for reporting. Please can you check whether a browser restart, as suggested by @CryoEM2, helps in your case also?
@CryoEM2 Do you observe delays every time during initial loading of the CryoSPARC page? Is the issue correlated with Chrome Relaunch to update prompts?
@shifral @CryoEM2 Please can you email us
- (please compress before attaching): browser console log and network har files (how?). Please include in the recording:
- a reload of the home screen
- navigation to projects page
- the tgz file created by the command
cryosparcm snaplogs
Please include in your email link to this discussion topic.
thank you for trying to get to the bottom of this. the issue is not persistent for me, having cropped up 3-4 times since the last ~month and I have no way to replicate the conditions. Hopefully we can get more info from shrifal, or I will try to provide more information if/when experiencing this again.
Seeing my issue again, I tried getting the console log. successfully typed the command and saw “undefined”, but cannot reload the page. Reviewing above, my issue and shrifal issue are different. My experience is that occasionally when I unplug hard line and switch to wifi, or switch from wifi to hard line, the cryosparc tabs won’t refresh for a few minutes. And if I try to open a new cryosparc it simnilarly hangs. They all have the spinning wheel in the tab and the screen shows the spinning wheel of 9 dots. Surely this is related to our security settings, but is relatively new issue. Eventually it loads but without error:
index.62001b1f.js:1 CryoSPARC
index.62001b1f.js:1 INFO initApp
index.257b9f50.js:1 browse-jobs Building filter query object took 0.10 milliseconds
index.62001b1f.js:1 INFO Authenticated onMount
index.62001b1f.js:1 INFO initData
index.62001b1f.js:1 INFO Init DDP 15k20QjDuKimjB2YWb4IS
index.62001b1f.js:1 command:core get_update_tag {}
index.62001b1f.js:1 command:core get_license_live_enabled {}
index.62001b1f.js:1 command:core get_license_ecl_enabled {}
index.62001b1f.js:1 command:core get_generate_intermediate_results_job_types {}
index.62001b1f.js:1 INFO Initialize debugApp
index.62001b1f.js:1 SUCCESS DDP server: connected 0
index.62001b1f.js:1 INFO Fetching initial browse data
index.62001b1f.js:1 INFO DDP server: loginResume {id: ‘6361d87f24ea3296be338588’, token: ‘15k20QjDuKimjB2YWb4IS’, tokenExpires: Sat May 03 2025 22:00:36 GMT-0700 (Pacific Daylight Time), type: ‘resume’}
index.62001b1f.js:1 data subscribe-ready: (direct) config args: (id: 1, elapsed: 426 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) scheduler args: (id: 2, elapsed: 428 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) allUsers args: (id: 3, elapsed: 431 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) queuedJobs args: (id: 4, elapsed: 431 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) activeJobs args: (id: 5, elapsed: 436 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) recentJobs args: (id: 6, elapsed: 442 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) allBlueprints args: (id: 7, elapsed: 443 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) allWorkflows args: (id: 8, elapsed: 443 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) notifications args: (id: 9, elapsed: 444 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) instanceStats args: (id: 10, elapsed: 444 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) applicableProjects args: (id: 11, elapsed: 444 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) currentJobs args: (id: 12, elapsed: 482 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) allTags args: (id: 13, elapsed: 483 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) starredProjects args: (id: 14, elapsed: 483 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) starredWorkspaces args: (id: 15, elapsed: 483 ms.)
index.62001b1f.js:1 data subscribe-ready: (direct) starredJobs args: (id: 16, elapsed: 484 ms.)
index.62001b1f.js:1 command:core get_license_live_enabled 1547.90 ms
index.62001b1f.js:1 command:core get_license_ecl_enabled 1586.10 ms
index.62001b1f.js:1 command:core get_generate_intermediate_results_job_types 1607.20 ms
index.62001b1f.js:1 command:core get_update_tag 1737.30 ms
index.62001b1f.js:1 data subscribe: currentBrowseProject currentProject args: [‘P328’]
index.62001b1f.js:1 data subscribe: currentBrowseWorkspace currentWorkspace args: (2) [‘P328’, ‘W2’]
index.62001b1f.js:1 data subscribe: SingleWorkspacePanel workspacePanel args: (2) [‘P328’, ‘W2’]
index.62001b1f.js:1 data subscribe-ready: currentBrowseProject currentProject args: [‘P328’] (id: 17, elapsed: 99 ms.)
index.62001b1f.js:1 data subscribe-ready: currentBrowseWorkspace currentWorkspace args: (2) [‘P328’, ‘W2’] (id: 18, elapsed: 99 ms.)
index.62001b1f.js:1 data subscribe-ready: SingleWorkspacePanel workspacePanel args: (2) [‘P328’, ‘W2’] (id: 19, elapsed: 95 ms.)
index.62001b1f.js:1 data subscribe: browseJobsFilteredCount jobsListCount args: [{…}]
index.62001b1f.js:1 data subscribe: browseJobsFullCount allBrowseJobsCount args: [{…}]
index.62001b1f.js:1 data subscribe-ready: browseJobsFilteredCount jobsListCount args: [{…}] (id: 20, elapsed: 98 ms.)
index.62001b1f.js:1 data subscribe-ready: browseJobsFullCount allBrowseJobsCount args: [{…}] (id: 21, elapsed: 100 ms.)
index.62001b1f.js:1 command:core set_user_viewed_workspace {user_id: ‘%CURRENT_USER%’, project_uid: ‘P328’, workspace_uid: ‘W2’}
index.62001b1f.js:1 data subscribe: cardViewJobs cardJobs args: (3) [0, 100, {…}]
index.257b9f50.js:1 browse-jobs Building filter query object took 0.00 milliseconds
Workflow.5aef1a55.js:1 cards-view Fetching static base jobs took 269 milliseconds
Workflow.5aef1a55.js:1 cards-view Computation of card layout took 0.40 milliseconds
index.62001b1f.js:1 command:core set_user_viewed_workspace 282.20 ms
index.62001b1f.js:1 data subscribe-ready: cardViewJobs cardJobs args: (3) [0, 100, {…}] (id: 22, elapsed: 916 ms.)
index.62001b1f.js:1 data subscribe-restart: cardViewJobs cardJobs 23 args: (3) [0, 0, {…}]
index.62001b1f.js:1 data subscribe-ready: cardViewJobs cardJobs args: (3) [0, 100, {…}] (id: 23, elapsed: 748 ms.)
index.62001b1f.js:1 data subscribe: workspaceJobGroups singleWorkspace args: (3) [‘P328’, ‘W2’, {…}]
index.62001b1f.js:1 data subscribe: cardViewJobsCreated cardJobsCreated args: (4) [Mon Feb 24 2025 10:36:06 GMT-0800 (Pacific Standard Time), ‘P328’, ‘W2’, {…}]
index.62001b1f.js:1 data subscribe: cardViewJobsDeleted cardJobsDeleted args: (4) [Mon Feb 24 2025 10:36:06 GMT-0800 (Pacific Standard Time), ‘P328’, ‘W2’, {…}]
index.62001b1f.js:1 data subscribe-ready: workspaceJobGroups singleWorkspace args: (3) [‘P328’, ‘W2’, {…}] (id: 24, elapsed: 97 ms.)
index.62001b1f.js:1 data subscribe-ready: cardViewJobsCreated cardJobsCreated args: (4) [Mon Feb 24 2025 10:36:06 GMT-0800 (Pacific Standard Time), ‘P328’, ‘W2’, {…}] (id: 25, elapsed: 102 ms.)
index.62001b1f.js:1 data subscribe-ready: cardViewJobsDeleted cardJobsDeleted args: (4) [Mon Feb 24 2025 10:36:06 GMT-0800 (Pacific Standard Time), ‘P328’, ‘W2’, {…}] (id: 26, elapsed: 103 ms.)
Does you cryosparc_master/config.sh already include the line
export CRYOSPARC_DISABLE_EXTERNAL_REQUESTS=true
?
If it does not, does adding that line and subsequently restarting CryoSPARC help?
it did not, and we finally were able to restart cryosparc (and update to the latest) and it also does not resolve this issue. Is it possibly Mac/Chrome/Security settings related?
@CryoEM2 Please can you post the outputs of the commands
free -h
nproc
and email us the tgz file created by the command
cryosparcm snaplogs
on the CryoSPARC master host. If you can, please also let us know date and time for periods where you observed page load disruption or delay.