Reduce processing time

[stephaniereinders]

On large x3p files (15+ MB), the app takes a while to compare two bullets. We could try replacing lapply and mapply calls with mclapply and mcmapply, respectively, or use other methods to run the code in parallel. Do we need to allow the user to choose whether to use parallel processing? If so, do we also need to allow the user to choose the number of cores?

[stephaniereinders]

mcapply might not be a good option for Shiny

The documentation for mclapply has the following warning:

"Warning
It is strongly discouraged to use these functions in GUI or embedded environments, because it leads to several processes sharing the same GUI which will likely cause chaos (and possibly crashes). Child processes should never use on-screen graphics devices. Some precautions have been taken to make this usable in R.app on macOS, but users of third-party front-ends should consult their documentation. Note that tcltk counts as a GUI for these purposes since Tcl runs an event loop. That event loop is inhibited in a child process but there could still be problems with Tk graphical connections."

[stephaniereinders]

shiny::ExtendedTask might be a good option

This article gives a short tutorial on using shiny::ExtendedTask in a Shiny app.