>  Am 10.06.2009, 15:00 Uhr, schrieb Michael Herger <slim@[...].net>:
>  
>  > Part of our software suite is a PerlApp packaged GUI application
>  > (using Wx). Due the used library the resulting file is rather large
>  > (~9MB).
>  >
>  > As we've had some complaints about slow startup, I've done some
>  > testing. In order to give an early visual feedback to the user, I've
>  > added a splash screen as early in the code as possible (simplified
>  > code):

[code snipped]

>  > Running this code from the source will give me the splash screen within a
>  > fraction of a second. Running the .exe file would take several seconds to
>  > get it shown. No matter whether I'm using any of the nocompress, clean or
>  > dyndll options. The simple timing ($x) would result in an approximately
>  > 50% longer runtime for the $useWx evaluation.
>  >
>  > Is this performance hit to be expected? Is there anything I can do to get
>  > the startup performance closer to the one running from source?

I did some trivial tests using the minimal.pl sample from the wxPerl
distribution and found that the compiled app would start within a
second or so when invoked the second and subsequent times.

So I wonder if the delay is specific to using wxPerl, or just the
general size of the application.

It is also not clear to me if you are using Wx::Perl::Packager or
some other mechanism to bundle the additional libraries.

I had given up on wxPerl a few years ago, as the code kept on changing
and playing evil tricks with the way it has to be loaded.  I've not kept
track, is Wx::Perl::Packager still needed?  I'm just guessing, but it
looks like I'm still getting errors that the temp directory cannot
be cleaned when I run a simple wrapped app that doesn't use W:P:P.

Cheers,
-Jan


_______________________________________________
PDK mailing list
PDK@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs