You are not logged in. [Log In] KiXtart.org website » Forums » KiXtart » Basic Scripting » SET command runs slow Windows 10
Register User       Forum List       Calendar       FAQ
Page 1 of 1 1
Topic Options
#210907 - 2015-11-09 03:00 PM SET command runs slow Windows 10
MMoore Offline
Just in Town

Registered: 2015-11-09
Posts: 4
Loc: NY
We have been using KiXtart for many years, running on Windows XP, Vista, Windows 7 & Windows 8, without any issues, script runs very fast, maybe 2 to 4 seconds to run. Recently we have upgraded a few devices to Windows 10 Enterprise. Now our Kix32 script takes about 90 seconds to run. I have narrowed it down to the "SET" command in our script file. We have 14 of them, and it takes about 85 seconds just to run those or 6 seconds each. Again, these were not an issue on any other versions of Windows that we have used these scripts on. Anyone have any ideas?

Thanks
Mark
Top
#210908 - 2015-11-09 08:02 PM Re: SET command runs slow Windows 10 [Re: MMoore]
NTDOC Administrator Offline
Administrator
*****

Registered: 2000-07-28
Posts: 11628
Loc: CA
What if you take a clean install of Windows 10 from a new hard drive instead of an upgrade.
Have seen many complaints from users with varying issues from upgrades. Clean installs don't seem to have the same reported issues.
Top
#210909 - 2015-11-09 08:14 PM Re: SET command runs slow Windows 10 [Re: NTDOC]
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 2001-06-05
Posts: 22346
Loc: OK
http://superuser.com/questions/565771/setting-user-environment-variables-is-very-slow

I think NTDoc is on to something with the upgrade being a possible culprit.
_________________________
!

download KiXnet

Top
#210911 - 2015-11-10 02:03 PM Re: SET command runs slow Windows 10 [Re: Lonkero]
MMoore Offline
Just in Town

Registered: 2015-11-09
Posts: 4
Loc: NY
I have a clean install Windows 10 Enterprise machine that I just tested this on. While it wasn't 6 seconds per SET command in my script, it still wasn't as quick as it was on any of the other OS's that we have used this on. I just tested it out and yes, it is a lot faster, almost 66% faster (takes about 2 seconds per set command). This in my opinion is too long. When I log in with the same account on any other Windows OS, the scripts takes about 1 seconds to complete.

Edited by MMoore (2015-11-10 02:04 PM)
Top
#210912 - 2015-11-10 06:40 PM Re: SET command runs slow Windows 10 [Re: MMoore]
NTDOC Administrator Offline
Administrator
*****

Registered: 2000-07-28
Posts: 11628
Loc: CA
I'm not yet running any Windows 10 in our environment so cannot properly test. Home user machines might be close enough but not sure. Also one thing to consider is that every single OS Microsoft has made has more hand holding and monitoring to make sure you the user or automated tasks are not doing something they should not be doing. I'm not saying that is the case here but it very well could be. You can trying running process explorer on it and see if it can track down a specific issue or not but in the long run a 2 second login script that is hidden in the first place really is not that long.
Top
#210913 - 2015-11-11 02:06 PM Re: SET command runs slow Windows 10 [Re: NTDOC]
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 2001-06-05
Posts: 22346
Loc: OK
Yea, but visible loginscript that takes minutes is. And his set takes 2s, not the script.
_________________________
!

download KiXnet

Top
#210914 - 2015-11-11 02:09 PM Re: SET command runs slow Windows 10 [Re: Lonkero]
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 2001-06-05
Posts: 22346
Loc: OK
To go back to the reason, set calls windows fun too that notifies programs of settings change. The slowness/fastness is by design and only Microsoft can change it.

If you want to change something faster, write the variables directly to registry.
_________________________
!

download KiXnet

Top
#210915 - 2015-11-11 05:31 PM Re: SET command runs slow Windows 10 [Re: Lonkero]
MMoore Offline
Just in Town

Registered: 2015-11-09
Posts: 4
Loc: NY
 Originally Posted By: Lonkero
To go back to the reason, set calls windows fun too that notifies programs of settings change. The slowness/fastness is by design and only Microsoft can change it.
If you want to change something faster, write the variables directly to registry.


I find that hard to believe, but it's MS, so I am not sure why I find it hard to believe. A CLEAN BUILD Windows 10 takes 2 seconds per set command, yet an Upgrade Windows 10 (from Windows 8 pro) takes 6 seconds per SET (before the upgrade, it took 0.1 seconds to run), yet, Windows 7 Pro (clean build) takes 0.1 seconds. If it was MS, then I can assume that all systems would behave similarly, yet they don't. Hopefully a solution will show up...
Top
#210916 - 2015-11-11 06:26 PM Re: SET command runs slow Windows 10 [Re: MMoore]
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 2001-06-05
Posts: 22346
Loc: OK
Dang auto correct. I can assure you "fun" was not the word written on this windows device.

Anywho. You can dig deeper by testing directly from the command line and from kix during and after logon process. If it has something to do with API kixtart calls, all of these will most likely give you different times.

If command line set takes forever too, then we are back to it is by design.
_________________________
!

download KiXnet

Top
#210917 - 2015-11-11 06:34 PM Re: SET command runs slow Windows 10 [Re: Lonkero]
Allen Administrator Offline
KiX Supporter
*****

Registered: 2003-04-19
Posts: 4562
Loc: USA
Not avoiding the problem, but curious about your use of SET. I can't think of a single script where I have ever used it. How/Why are you using those. Maybe we can suggest a better method.
Top
#210918 - 2015-11-11 09:17 PM Re: SET command runs slow Windows 10 [Re: Allen]
Glenn Barnas Administrator Offline
KiX Supporter
*****

Registered: 2003-01-28
Posts: 4401
Loc: New Jersey
I was thinking the same thing, Allen...
_________________________
Actually I am a Rocket Scientist! \:D

Top
#210919 - 2015-11-12 02:22 PM Re: SET command runs slow Windows 10 [Re: Lonkero]
MMoore Offline
Just in Town

Registered: 2015-11-09
Posts: 4
Loc: NY
 Originally Posted By: Allen
Not avoiding the problem, but curious about your use of SET. I can't think of a single script where I have ever used it. How/Why are you using those. Maybe we can suggest a better method.

 Originally Posted By: Glenn Barnas
I was thinking the same thing, Allen...

we use environment variables in our software (we are a software development company). These environment variables are needed for our legacy software to run correctly. So, while you might not use them, we do, and not using them should not be a reason why we notice a performance different from one OS to another on the same network/domain running the exact same script.

 Originally Posted By: Lonkero
Dang auto correct. I can assure you "fun" was not the word written on this windows device.
Anywho. You can dig deeper by testing directly from the command line and from kix during and after logon process. If it has something to do with API kixtart calls, all of these will most likely give you different times.
If command line set takes forever too, then we are back to it is by design.



Windows command SetX is also very slow (6 seconds to run). I have done some digging on the web, to no avail for a solution.
Top
#210920 - 2015-11-12 03:02 PM Re: SET command runs slow Windows 10 [Re: MMoore]
BradV Offline
Seasoned Scripter
****

Registered: 2006-08-16
Posts: 687
Loc: Maryland, USA
Right, but shouldn't environment variables be set up in user's context? I would just have one or more central files that each user's login would source to get the required environment variables. You shouldn't have to change them at every login. That is, you would only need to change when you:

1. Install a new version, or
2. Move the software to a new location or new server.

and then you would just edit those central file(s) once.
Top
#210922 - 2015-11-12 08:01 PM Re: SET command runs slow Windows 10 [Re: BradV]
Glenn Barnas Administrator Offline
KiX Supporter
*****

Registered: 2003-01-28
Posts: 4401
Loc: New Jersey
Doing software dev, I also rely heavily on env variables. I'll clear them and run some tests on two of our laptops - we have one with Win-7 and the other with Win-10, both with the same model/configuration, so the comparison should be on-par.

We do use the "SetM()" function to set the variables permanently using a config process. If I were to run it during logon, I'd track a version in the registry and exit the config script if the version was at or above, and perform the updates if it were below.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D

Top
Page 1 of 1 1


Moderator:  Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart 
Hop to:
Shout Box

Who's Online
0 registered and 934 anonymous users online.
details
Newest Members
StuTheCoder, M_Moore, BeeEm, min_seow, Audio
17884 Registered Users
My Cookies · Mark all read Powered by UBB.threads™ Contact Us · KiXtart.org website · Top

Generated in 0.162 seconds in which 0.112 seconds were spent on a total of 13 queries. Zlib compression enabled.
Search the board with:
superb Board Search
or try with google:
Google
Web kixtart.org