PitStop Server Takes ages to process files _SOLVED

[victor Lukenga]

Hi everyone!



I've got a problem : files are taking long time to process in PSS
I don't know why : most of these files are between 2 and 10 mb

more over all other jobs are stuck

any idea ?

I have 1 conccurent processor
I running switch on windows 10

[bens]

Hi,

The processing speed is very dependent on the contents of the file, and what you do with it. For example running only an action to check the colour space on a file of 4 GB which only contains a single, very large image will process very quickly. On the other hand a 2 MB file with millions of paths will take a while.

That said, there may be some things you can do to optimize your workflow. PitStop Server is optimized to work on several files simultaneously, so processing one file at a time will be slower than multiple files at once. Some recommendations:

- Make sure you have the latest version of both Switch and PitStop Server.
- Start PitStop Server before starting your flows. This way you ensure that the PitStop Server engine will be used to process, which is faster than using the CLI.
- Close the PitStop Server UI, but make sure the engine keeps running. If the UI is open, extra communication is needed between the different components.
- Set both the PitStop Server and Switch preferences for concurrent processing correctly. A good rule of thumb is: 1 concurrent process per CPU core, plus 1 extra. For example a quad core machine would have 5 concurrent processes. Note that this is just a rule of thumb, the ideal number will depend on your hardware and the type of jobs you do.
- Use the 64 bit PitStop Server.
- Make sure you have enough RAM, and a fast hard disk.

Hope this helps,
bens

[victor Lukenga]

Hi Bens

Thank you to answer.

I think that I figure this out this night : I've set Concurrent processes to 4 in switch ( vs 9 in PSS) now instead seeing job per job
I can see 4 lines wich are processed in same time

for that 2mb file (rasterized) I also figure out why it takes 605 seconds to process : i set "check for ink coverage" on preflight ; this operation is quite long, perhaps I will have to find an alternative to check up amount of ink

Most of time PSS ui is closed and run in CLI by default I guess ? How to make sure that PSS don't process in CLI?

Last word about my config : PSS and switch 64 is installed on a windows 10 PC ,16 GB RAM and a hybrid HDD

since this mornig I don't have any performances issues: I can consider that this problem is solved for the moment! thanks for advices

Something Else
Bens, Can you help me to create an Xml from scratch (Scripting,easier for me or Saxon I have pain to understand XSLT Stylesheet making): the idea is to take an existing dataset remove unwanted nodes and add specific node based on some parameters previously set (e.g. warning or error report...)

Cheers

[bens]

Most of time PSS ui is closed and run in CLI by default I guess ? How to make sure that PSS don't process in CLI?

The CLI will always be used if you use Switch, but that's not a problem. As long as PitStop Server is running in the background, you're using the most optimal setup.

since this mornig I don't have any performances issues: I can consider that this problem is solved for the moment!

Good

Bens, Can you help me to create an Xml from scratch (Scripting,easier for me or Saxon I have pain to understand XSLT Stylesheet making): the idea is to take an existing dataset remove unwanted nodes and add specific node based on some parameters previously set (e.g. warning or error report...)

I suggest you make a new post about this, I'm sure someone will be able to help you with either an xslt or a script