Currently, my CS version is 4.5.3. And creating new jobs, copy jobs, or scroll up and down etc. are very slow or lagging now. Other sofewares on my computer don’t have this issue. Restarting computer doesn’t help. Do you have any idesa?
@CleoShen Please can you post:
- the full URL (including
http:orhttps:and port number, if applicable) that you enter into the web browser’s address bar to access the CryoSPARC GUI - the output of the following commands:
cryosparcm log supervisord | tail -n 30 ps -eo pid,ppid,start,command | grep -e cryosparc -e mongo
@CleoShen CS can slow down over time and we do restart. It seems much faster after that.
Is it just chrome or does another web browser seem faster ?
With some default security, the web browser may think cryosparc host:39000 is insecure - especially with downloads.
Let us know how the new v4.60 goes.
A1: http://localhost:16711/
A2:
2024-09-09 13:26:20,614 INFO supervisord started with pid 30081
2024-09-09 13:26:45,364 INFO spawned: 'database' with pid 30217
2024-09-09 13:26:46,411 INFO success: database entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-09 13:26:53,571 INFO spawned: 'command_core' with pid 30333
2024-09-09 13:26:58,579 INFO success: command_core entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2024-09-09 13:27:33,662 INFO spawned: 'command_vis' with pid 30437
2024-09-09 13:27:34,666 INFO success: command_vis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-09 13:27:35,023 INFO spawned: 'command_rtp' with pid 30449
2024-09-09 13:27:36,193 INFO success: command_rtp entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-09 13:27:58,811 INFO spawned: 'app' with pid 30532
2024-09-09 13:27:59,814 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-09 13:28:00,498 INFO spawned: 'app_api' with pid 30544
2024-09-09 13:28:01,534 INFO success: app_api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-09 14:29:30,785 INFO RPC interface 'supervisor' initialized
2024-09-09 14:29:30,785 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-09-09 14:29:30,786 INFO daemonizing the supervisord process
2024-09-09 14:29:30,794 INFO supervisord started with pid 7652
2024-09-09 14:29:49,836 INFO spawned: 'database' with pid 7818
2024-09-09 14:29:50,881 INFO success: database entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-09 14:29:58,446 INFO spawned: 'command_core' with pid 7951
2024-09-09 14:30:03,454 INFO success: command_core entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2024-09-09 14:30:24,575 INFO spawned: 'command_vis' with pid 8081
2024-09-09 14:30:25,577 INFO success: command_vis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-09 14:30:25,976 INFO spawned: 'command_rtp' with pid 8098
2024-09-09 14:30:27,156 INFO success: command_rtp entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-09 14:30:43,869 INFO spawned: 'app' with pid 8196
2024-09-09 14:30:44,872 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-09 14:30:45,369 INFO spawned: 'app_api' with pid 8215
2024-09-09 14:30:47,280 INFO success: app_api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)`
A2-2:`5648 5594 16:08:19 bash /home/groups/brunger/software/cryosparc/cryosparc_worker/bin/cryosparcw run --project P3 --job J2396 --master_hostname sh02-13n07.int --master_command_core_port 39008
5669 5648 16:08:21 python -c import cryosparc_compute.run as run; run.run() --project P3 --job J2396 --master_hostname sh02-13n07.int --master_command_core_port 39008
5671 5669 16:08:22 python -c import cryosparc_compute.run as run; run.run() --project P3 --job J2396 --master_hostname sh02-13n07.int --master_command_core_port 39008
6513 5362 16:18:06 grep --color=auto -e cryosparc -e mongo
7652 1 Sep 09 python /home/groups/brunger/software/cryosparc/cryosparc_master/deps/anaconda/envs/cryosparc_master_env/bin/supervisord -c /home/groups/brunger/software/cryosparc/cryosparc_master/supervisord.conf
7818 7652 Sep 09 mongod --auth --dbpath /home/groups/brunger/software/cryosparc/cryosparc_database --port 39007 --oplogSize 64 --replSet meteor --wiredTigerCacheSizeGB 4 --bind_ip_all
7951 7652 Sep 09 python /home/groups/brunger/software/cryosparc/cryosparc_master/deps/anaconda/envs/cryosparc_master_env/bin/gunicorn -n command_core -b 0.0.0.0:39008 cryosparc_command.command_core:start() -c /home/groups/brunger/software/cryosparc/cryosparc_master/gunicorn.conf.py
8008 7951 Sep 09 python /home/groups/brunger/software/cryosparc/cryosparc_master/deps/anaconda/envs/cryosparc_master_env/bin/gunicorn -n command_core -b 0.0.0.0:39008 cryosparc_command.command_core:start() -c /home/groups/brunger/software/cryosparc/cryosparc_master/gunicorn.conf.py
8081 7652 Sep 09 python /home/groups/brunger/software/cryosparc/cryosparc_master/deps/anaconda/envs/cryosparc_master_env/bin/gunicorn cryosparc_command.command_vis:app -n command_vis -b 0.0.0.0:39009 -c /home/groups/brunger/software/cryosparc/cryosparc_master/gunicorn.conf.py
8098 7652 Sep 09 python /home/groups/brunger/software/cryosparc/cryosparc_master/deps/anaconda/envs/cryosparc_master_env/bin/gunicorn cryosparc_command.command_rtp:start() -n command_rtp -b 0.0.0.0:39011 -c /home/groups/brunger/software/cryosparc/cryosparc_master/gunicorn.conf.py
8100 8081 Sep 09 python /home/groups/brunger/software/cryosparc/cryosparc_master/deps/anaconda/envs/cryosparc_master_env/bin/gunicorn cryosparc_command.command_vis:app -n command_vis -b 0.0.0.0:39009 -c /home/groups/brunger/software/cryosparc/cryosparc_master/gunicorn.conf.py
8116 8098 Sep 09 python /home/groups/brunger/software/cryosparc/cryosparc_master/deps/anaconda/envs/cryosparc_master_env/bin/gunicorn cryosparc_command.command_rtp:start() -n command_rtp -b 0.0.0.0:39011 -c /home/groups/brunger/software/cryosparc/cryosparc_master/gunicorn.conf.py
8215 7652 Sep 09 /home/groups/brunger/software/cryosparc/cryosparc_master/cryosparc_app/nodejs/bin/node ./bundle/main.js
After re-starting my Chrome, it would be faster, but, after creating like three four ish jobs, it starts to be lagging again.
Thanks for posting these outputs.
The symptoms do not exactly match a problem that should be fixed by either a patch for v4.5.3 or, following @Mark-A-Nakasone’s suggestion, an update to v4.6.0, but you may want to try patching or updating anyway.
Given the port number outside the port range of the CryoSPARC master processes shown in your log and ps outputs, does your browser run on a computer other than the CryoSPARC master, and you forwarded a port from the “browser computer” with an ssh command like
ssh -L 16711:[...]
?
1 Like
Yes, the CS master ran on computer cluster and I use my local computer to see the GUI. I used ssh like command to start the browser GUI.
Is this still happening after the update to v4.6.0?