Creating workflow very slow or not responsive

Automated Workflows
1

I have a 52 jobs and tried to create a workflow in Cryosparc v5.0.2.

When I clicked Create Workflow, it seems like almost nothing happening. When I disconnected and connected again, I can create a workflow for a simple 4-5 jobs but it seems unresponsive when 10-15 jobs selected. I think this is specific to performance in v5 or perhaps our server’s performance as I can creat a workflow with ~20 jobs before with ease in v4

Any way that I create workflow on my system?

2

Just want to do a bit of update.

When I did this using Chrome, it is non-responsive. I switched to Safari and everything is ok. So it is due to something about the web app with Chrome.

3

@builab Please can you post the details mentioned in cryoSPARC v5-beta user interface feels slow - #6 by wtempel about the URL that you entered into your web browser’s address bar to access the CryoSPARC UI?

4

I use http://localhost:9999 to access cryosparc installed on a server remotely from my laptop. Chrome doesn’t allow me to create workflow but Safari is ok.

cryoSPARC v5-beta user interface feels slow
5

Please can you post the output of this command (on your laptop)
host localhost
and let us know whether you are using local port forwarding?

6

$host localhost

localhost has address 127.0.0.1

localhost has IPv6 address ::1

I use local port forwarding using the command:
ssh -N -f -L localhost:9999:localhost:xxxx user@server

7

Thanks @builab for these details. Please can you also

  1. let us know the version of Chrome chrome://version
  2. the types and versions of any installed Chrome extensions chrome://extensions/
  3. confirm whether the stall occurs at the Create Workflow action or when you press Apply.
  4. record browser console and network outputs while performing the action that is being delayed. Please email us the compressed outputs. I’ll let you know the email address in a personal message.
8

Version here:
Google Chrome 147.0.7727.101 (Official Build) (arm64)
Revision 56536d2a8034c51b0e68e1a0483ab9f1a0165ae3-refs/branch-heads/7727@{#2927}
OS macOS Version 15.7.3 (Build 24G419)
JavaScript V8 14.7.173.19
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36
Command Line /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --flag-switches-end --origin-trial-disabled-features=CanvasTextNg|WebAssemblyCustomDescriptors
Executable Path /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path /Users/kbui2/Library/Application Support/Google/Chrome/Default
Linker lld
Command-line Variations eyJkaXNhYmxlLWZlYXR1cmVzIjoiQXV0b2ZpbGxBZGRyZXNzSW1wcm92ZUJ1…
Active Variations 32806e4f-51f6de0b
e2052757-1f8c5973 …

Extension: Adblock, Adobe Acrobat, Checker Plus for Google Calendar, Cisco Webex, Endnote Click, Evernote Web Clipper, GitZip for github, Google DocOffline, Google Scholar Button, WordTune, Grammarly, Teleparty, Porto - Import Tweets to BlueSky

  1. The stall occurs at the Create Workflow action, not Apply.

  2. I am recording and sending now.

9

Hi @builab,

We were able to find an out of memory error in your logs, and were then able to reproduce the same error when attempting to create a workflow from jobs where an input “cycle” exists.

This would be a rare case where an output from a job, lets say Job A, was connected to the input of another job, Job B, and then an output from Job B was connected back to Job A. We have observed this in rare cases where the builder was still engaged for a sibling job and an input is inserted from its parent.

Would you be able to check your selection of jobs for such a connection? We were able to reproduce by connecting micrographs from a Patch Motion Correction job to a Patch CTF job, and then connecting exposures from that same Patch CTF job back to the Patch Motion Correction job.

- Kelly

10

Thanks. I definitely don’t have that since I was able to create the Workflow using Safari. Since then, I haven’t had the same problem again.