Re: Performance issues in Chrome and Firefox - Page 2

DavidU54339-XRX · ‎03-26-2020

I have been able to recreate the Join problem. I have written a BUG against it. You can also contact Xerox support and have them write up the problem -- customer complaints have more weight than development problem reports.

barwapk · ‎03-26-2020

Workflow looks like this:

https://ibb.co/8NZ15XK

And after submitting job is paused:

https://ibb.co/vLRdN7y

I cant press "Resume Job" and if I press cancel Core will crash and I have to restart Core serwer.

In previows version of Core it worked, Join node has a "collect jobs" option, now (new version of Core) it is default. If I change Join to Collect (for 1 minute) it is working but I dont wont to wait 1 minute..

How can I share a workflow file?

DavidU54339-XRX · ‎03-21-2020

The Join and Collect nodes were not changed. Can you describe the problem you've encountered?

barwapk · ‎03-21-2020

There was some changes in Join node? I have workflow with Join and collect selected in it and now it is not working like earlier.

barwapk · ‎03-18-2020

Im sorry, "The GUI is a bit slower"? Editing nodes is 10 times slower... I have waited long for HTML version and now it is much worse than SilverLight version :(

DavidU54339-XRX · ‎03-14-2020

I was referring to the version that you used with Chrome/Firefox (e.g., 5.3.0).

I do not see issues with 5.4.2 for job processing. The GUI is a bit slower than Silverlight (5.1.0.9). Of course your job processing may yield different results.

barwapk · ‎03-13-2020

5.1.0.9

DavidU54339-XRX · ‎03-13-2020

What release did you previously try?

barwapk · ‎03-13-2020

Im getting to install Core 5.4 are there still issues with preformance?

mpeters · ‎10-31-2019

You are not alone. I have reported a similar issue. See here:

https://forum.support.xerox.com/t5/FreeFlow-Core/Slow-performance-with-5-3-0/td-p/227339

I have also contacted support and they are monitoring the issue on our installation and made some suggestions regarding not closing our browser as it affects the cache, and also changing the setting for simultaneous running jobs, but we have not seen a noticable change in the issue. We have the problem with any browser: Chrome, Firefox, Safari, and Edge. Happens on both PC and Mac. We also see a slowdown in actual job processing. A restart temporarily fixes the problem, but it returns usually within a day.