cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
vikram
Level 3

InstallShield 2014 setup.exe takes more time compared to IS 12

InstallShield 2014 setup.exe takes more time compared to IS 12.

I had ported an IS 12 project to IS 2014 premier version.
While silent installation with same set of parameters I found that New Setup.exe takes more time to get installed.
While MSI running time is same.but time taken by setup.exe to run .msi is increased considerably.
The analysis found that setup is creating .tmp files and some other files in windows %temp% folder before running .msi.
But these operations are less in case of IS 12 moreover no .tmp files are getting created in IS 12 installer.

Following is the process explorer logs for extra operations in IS 2014

12:04:03.0177839 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 92,160, Length: 10,240
12:04:03.0178508 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 102,400, Length: 10,240
12:04:03.0179253 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 112,640, Length: 10,240
12:04:03.0180520 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 122,880, Length: 10,240, Priority: Normal
12:04:03.0182536 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 133,120, Length: 10,240
12:04:03.0183313 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 143,360, Length: 10,240
12:04:03.0184340 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 153,600, Length: 10,240
12:04:03.0185025 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 163,840, Length: 10,240
12:04:03.0185691 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 174,080, Length: 10,240
12:04:03.0186593 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 184,320, Length: 10,240
12:04:03.0187677 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 194,560, Length: 10,240, Priority: Normal
12:04:03.0189879 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 204,800, Length: 10,240
:
:
:
12:04:03.0905978 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
12:04:03.0906931 AM setup.exe 3668 LockFile C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS Exclusive: False, Offset: 0, Length: 4,294,967,295, Fail Immediately: False
12:04:03.0907197 AM setup.exe 3668 QueryStandardInformationFile C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS AllocationSize: 672, EndOfFile: 669, NumberOfLinks: 1, DeletePending: False, Directory: False
12:04:03.0907674 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS Offset: 0, Length: 669, Priority: Normal
12:04:03.0908710 AM setup.exe 3668 UnlockFileSingle C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS Offset: 0, Length: 4,294,967,295
12:04:03.0908928 AM setup.exe 3668 CloseFile C:\Users\Client\AppData\Local\Temp\{37626276-B7B7-4EED-818A-F1BE8ED40A2A}\IsConfig.ini SUCCESS
12:04:03.0910342 AM setup.exe 3668 CloseFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS
12:04:03.0914248 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\{42F97B6F-1E30-415A-A1A1-C363702B140E} SUCCESS Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0, OpenResult: Created
12:04:03.0918120 AM Explorer.EXE 320 NotifyChangeDirectory C:\Users\Client\AppData\Local\Temp SUCCESS Filter: FILE_NOTIFY_CHANGE_DIR_NAME
12:04:03.0922202 AM Explorer.EXE 320 NotifyChangeDirectory C:\Users\Client\AppData\Local SUCCESS Filter: FILE_NOTIFY_CHANGE_FILE_NAME, FILE_NOTIFY_CHANGE_ATTRIBUTES, FILE_NOTIFY_CHANGE_LAST_WRITE
12:04:03.0932159 AM setup.exe 3668 CloseFile C:\Users\Client\AppData\Local\Temp\{42F97B6F-1E30-415A-A1A1-C363702B140E} SUCCESS
12:04:03.0936920 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI NAME NOT FOUND Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Disallow Exclusive, Attributes: R, ShareMode: Read, AllocationSize: n/a
12:04:03.0940746 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI SUCCESS Desired Access: Generic Write, Read Attributes, Disposition: OverwriteIf, Options: Synchronous IO Non-Alert, Non-Directory File, Disallow Exclusive, Attributes: N, ShareMode: Read, AllocationSize: 0, OpenResult: Created
12:04:03.0946678 AM Explorer.EXE 320 NotifyChangeDirectory C:\Users\Client\AppData\Local\Temp SUCCESS Filter: FILE_NOTIFY_CHANGE_FILE_NAME, FILE_NOTIFY_CHANGE_ATTRIBUTES, FILE_NOTIFY_CHANGE_LAST_WRITE
12:04:03.0948752 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI SUCCESS Offset: 0, Length: 2, Priority: Normal
12:04:03.0950543 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI SUCCESS Offset: 2, Length: 22, Priority: Normal
12:04:03.0951580 AM setup.exe 3668 WriteFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI SUCCESS Offset: 24, Length: 228, Priority: Normal
12:04:03.0952210 AM setup.exe 3668 CloseFile C:\Users\Client\AppData\Local\Temp\{8D2C264F-648C-4E84-8415-1D6C6F5F79D4}\_ISMSIDEL.INI SUCCESS
12:04:03.0957128 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Disallow Exclusive, Attributes: N, ShareMode: Read, AllocationSize: n/a, OpenResult: Opened
12:04:03.0958136 AM setup.exe 3668 CreateFileMapping C:\Users\Client\AppData\Local\Temp\issDDD9.tmp FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection: PAGE_READONLY
12:04:03.0958312 AM setup.exe 3668 QueryStandardInformationFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS AllocationSize: 4,407,296, EndOfFile: 4,406,977, NumberOfLinks: 1, DeletePending: False, Directory: False
12:04:03.0958673 AM setup.exe 3668 CreateFileMapping C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS SyncType: SyncTypeOther
12:04:03.0959595 AM setup.exe 3668 CloseFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS
12:04:03.0963351 AM setup.exe 3668 CreateFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Disallow Exclusive, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened
12:04:03.0964250 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 604,160, Length: 46, Priority: Normal
12:04:03.0965197 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 604,206, Length: 24
12:04:03.0965581 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 604,230, Length: 18
12:04:03.0965942 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 791,435, Length: 24
12:04:03.0966269 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 791,459, Length: 16
12:04:03.0966601 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,077,291, Length: 24
12:04:03.0967052 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,077,315, Length: 24
12:04:03.0967404 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,155,287, Length: 24
12:04:03.0967657 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,155,311, Length: 24
12:04:03.0967993 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,291,348, Length: 24
12:04:03.0968252 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,291,372, Length: 34
12:04:03.0968614 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,453,129, Length: 24
12:04:03.0968931 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,453,153, Length: 34
12:04:03.0969270 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,615,039, Length: 24
12:04:03.0969558 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,615,063, Length: 34
12:04:03.0969929 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,780,723, Length: 24
12:04:03.0970204 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,780,747, Length: 34
12:04:03.0970578 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,947,027, Length: 24
12:04:03.0970879 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 1,947,051, Length: 34
12:04:03.0971253 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 2,146,494, Length: 24
12:04:03.0971845 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 2,146,518, Length: 34
12:04:03.0972226 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 2,312,305, Length: 24
12:04:03.0972492 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 2,312,329, Length: 34
12:04:03.0972901 AM setup.exe 3668 ReadFile C:\Users\Client\AppData\Local\Temp\issDDD9.tmp SUCCESS Offset: 2,479,368, Length: 24

.......


Does anyone has any idea on this or how to avoid these extra operations in IS 2014.

Thanks.
Labels (1)
0 Kudos
(6) Replies
MichaelU
Level 12 Flexeran
Level 12 Flexeran

I'm unclear what you're trying to report or ask here. If I'm reading your post correctly, you've highlighted an operation that takes less than 1/10 of one second, from 12:04:03.0177839 to 12:04:03.0972901. Could you clarify what overall problem you are facing? Perhaps a statement like for a XXX meg compressed setup.exe, it takes YYY seconds in InstallShield 2014 instead of ZZZ seconds in InstallShield 12 to show the InstallWelcome dialog after launching setup.exe would better explain this.

(I'm less concerned with raw read/write traces than with reasonable overall clock times for the sizes in question. I believe the raw steps you describe are related to enhanced compression that was added since InstallShield 12.)
0 Kudos
vikram
Level 3

Hi MichaelU

Thank you very much for your input.

I will elaborate the problem.


Background:
I had few CD-ROM installer Projects for some desktop applications which were built using InstallShield12.
Now we have ported all those projects to InstallShield 2014 Premier version.

Now the next thing is we have another C++ based application(like a suite installer) where we call these Installers Setup.exe silently provoding few command-line options based on users selection of the application.

problem
Now from this Suite installer like Application... If I use InstallShield12 built Installers, installing them takes lesser time than using InstallShield 2014 built Installers.
This time difference is significant(keeping the same environment of h/w and OS.)


Observation

Analyzing further, by checking MSI Logs I observed that MSI running time for the same application built in IS12 and IS 2014 is same.
But the time-gap between to continues MSI runs is significantly larger with IS2014 built application

now by checking in process explorer i found that this time is consumed between the actual call of Setup.exe to the call of MSI and then after MSI returns then again Setup.exe ends after a few seconds(3 seconds on an average).


ApplicationA(Setup.exe)-->ApplicationA MSI-->ApplicationA(Setup.exe) then ApplicationB(Setup.exe)-->ApplicationB MSI-->ApplicationB(Setup.exe).....so on

the arrows(-->) show the extra time taken in InstallShield 2014 built Installers.(one arrow costs 3 seconds of time approxomately)

So for one application install the time increased is 6 seconds(setup.exe--->xxx.msi--->setup.exe)


Quoting to your query,
>>If I'm reading your post correctly, you've highlighted an operation that takes less than 1/10 of one second, from 12:04:03.0177839 to 12:04:03.0972901.
these 1/10th of a second operations collectively turns in considerable time gap nearly 4-5 seconds.

and then again some operations like mentioned earlier.

I dont know if these are some checks added for InstallShield 2014 .

Please provide some inputs.
0 Kudos
vikram
Level 3

Now another issue is:
With an Antivirus Software named"Virus Buster" installed at the target machine,the InstallShield 2014 built installers takes longer time in installation than the InstallShield12 built installers. this time difference is considerable.

The same issue is seen by another project which has been ported from InstallShield 12 to InstallShield2010.
Checking the MSI logs I could see that there is no extra action taking place, rather creation and closing of MSI Handle is consuming extra time.
Aggregating all such time gaps it turns into huge delay.

Any inputs... or in case if this is known issue for all the InstallShield versions released after InstallShield12?
0 Kudos
MichaelU
Level 12 Flexeran
Level 12 Flexeran

I haven't heard of this before; in fact I hadn't even heard of Virus Buster before today. Wikipedia claims it was cancelled after August 2012, however, so I'm not sure I would consider it an effective solution.

If you have confirmed that uninstalling Virus Buster resolves the performance difference between InstallShield 2014 and InstallShield 12, then I would suspect a problem with the anti-virus software that is somehow revealed by recent versions of InstallShield.
0 Kudos
vikram
Level 3

Hi MichaelU,

Thanks for your inputs.

Quoting to your line"If you have confirmed that uninstalling Virus Buster resolves the performance difference between InstallShield 2014 and InstallShield 12"

The difference in performance exists even without Virus Buster installed on my system.

With Virus Buster this additional delay is an add-on on the existing problem.

My tests for one particular application installer are as:

InstallShield 2014 built Installer: 22 seconds(without Virus Buster installed) & 65 seconds (with Virus Buster installed)

However,

InstallShield 12 built Installer: 13 seconds(without Virus Buster installed) & 17 seconds (with Virus Buster installed)

(the system configuration and the OS environment has been kept constant)



Thanks,
Vikram
0 Kudos
DLee65
Level 13

Is there any chance that in releases view that the compression setting has changed between the two versions? I know that our installation speed is affected by the compression ratio for the setup.exe. I am probably way out in left field on this but it is something to consider. For our use we use the least amount of compression for a single setup.exe.
0 Kudos