in reply to faster start of "exe" generated by pp

In case the problem is that the system's temp space is being cleaned up on reboot, you might want to tell PAR to unpack into a different directory by setting PAR_GLOBAL_TEMP.  See also Notes.

  • Comment on Re: faster start of "exe" generated by pp

Replies are listed 'Best First'.
Re^2: faster start of "exe" generated by pp
by Dirk80 (Pilgrim) on Apr 07, 2011 at 07:29 UTC

    Thank you all for your answerws.

    PAR_GLOBAL_TEMP really helps to control where the exe-file is unpacked. But it does NOT solve the problem.

    Although the folder with the unpacked files is still available after a restart it takes some seconds until the exe-file is executed.

      But it does NOT solve the problem.

      Then maybe the issue you really have is not the unpacking, but rather that first-time starts of the exe do not have the advantage of files and shared libraries already having been cached/buffered in memory by the OS, as subsequent starts would have.

      There's not a lot you can do in this case...

        I could see one thing - but it just folds the application startup into the machine startup. It isn't really making the time better, just having it happen at a time when you are less likely to be impacted.

        Have a way to just run the application with a no-op to have the OS cache the libraries and files as part of your startup sequence.

        --MidLifeXis