V13 watchlist very slow

Technical support and scripting issues

Moderators: Dorian (MJT support), JRL

Post Reply
User avatar
Djek
Pro Scripter
Posts: 147
Joined: Sat Feb 05, 2005 11:35 pm
Location: Holland
Contact:

V13 watchlist very slow

Post by Djek » Sun Nov 20, 2011 8:26 am

hi all,
i'm exploring the magnificent possibilities of V13 and I notice that the watchlist is building the list very slow and it is unuseable.
I ve reinstalled v13.0.00, imported all macro's from scratch, but the watchlist stil reacts very slow.
Are there more of you experiencing this problem?

Thanks !
kind regards
Djek

EDIT: I think it has to do with the presence of array's in the watchlist, if i scroll the watchlist, when it arrives to the arrays it takes some time to re-group them . I f the array is huge (900) then it takes 10 secondes.
Last edited by Djek on Sun Nov 20, 2011 7:03 pm, edited 1 time in total.

User avatar
Rain
Automation Wizard
Posts: 550
Joined: Tue Aug 09, 2005 5:02 pm
Contact:

Post by Rain » Sun Nov 20, 2011 4:56 pm

Speed is fine on my system.

Windows 7 Ultimate SP 3

RAM 6 GB

User avatar
Marcus Tettmar
Site Admin
Posts: 7380
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Post by Marcus Tettmar » Mon Nov 21, 2011 10:35 am

One of our main aims with v13 was to make the watch list FASTER, and one of the ways we've done that is to make arrays only show the container name and allow you to drill down on them. In v12 and earlier debugging could get painfully slow if you had code that created large arrays. In v13 there is now no delay.

Aside from that there are no changes that should make it slower and we certainly haven't noticed any slowdowns during testing or since.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

User avatar
JRL
Automation Wizard
Posts: 3501
Joined: Mon Jan 10, 2005 6:22 pm
Location: Iowa

Post by JRL » Mon Nov 21, 2011 7:08 pm

This thread made me wonder whether I could overwhelm the watchlist. So...

From the editor, just ran a select all query on a large database. I try not to do this normally because it does take a while. After about 5 minutes the query returned 22557 records each with 41 fields, that totals 924,837 variables. The watchlist is still responsive even with nearly a million variables assigned.

Picked the plus beside the variable to display all 900K variables. This again topk about 5 minutes, but after the display completed the watchlist was again instantly responsive. Although, now that I have this massive variable count, each press of F8 to step through the script takes about 3 seconds. I suppose that's understandable.

Dell Inspiron laptop, Dual core 2.4 Ghz Pentium with 2 Gig RAM. Win XP SP3. Macro Scheduler v13.0.00

User avatar
Djek
Pro Scripter
Posts: 147
Joined: Sat Feb 05, 2005 11:35 pm
Location: Holland
Contact:

Post by Djek » Mon Nov 21, 2011 8:08 pm

Ok, thanks for the input, but now i'm curious ! :

I managed to break down my script to the bottleneck, and i would be very pleased if you try to run this script to the breakpoint, wait for 5 secondes and then scroll trough the watchlist.
Beware that it creates a file on c:\temp
With this script my watchlist is very slow. (Compaq NX6110)
I havent try this on a other laptop.
Thanks!

Code: Select all

let>weeknr=44
let>pad=c:\temp
HTTPRequest>http://www.curatoren.nl/fo/verslag_overzicht.php?weeknr=2011%weeknr%,%pad%\weeknr%weeknr%.txt,GET,,strHTML,,,,


ReadFile>%pad%\weeknr%weeknr%.txt,inlees
Separate>inlees,<td><a href=',inlees_stuk

**BREAKPOINT**

label>einde


kind regards,
Djek

User avatar
JRL
Automation Wizard
Posts: 3501
Joined: Mon Jan 10, 2005 6:22 pm
Location: Iowa

Post by JRL » Mon Nov 21, 2011 8:49 pm

Your script works normally for me using release 13. Tried it in release 12 also and had no issues there either.

User avatar
Djek
Pro Scripter
Posts: 147
Joined: Sat Feb 05, 2005 11:35 pm
Location: Holland
Contact:

Post by Djek » Mon Nov 21, 2011 9:04 pm

wel thanks for testing,
there must be something wrong over here, If I scroll, or watch the array everything gets stuck and stacato.
Hm stupid of me to first remove V12, I now know that these versions can work both seperate. I allready reinstalled V13, so next step is to remove V13, reinstall V12 and then reinstall V13.
Well its sure foggy over here, but this must wait for a rainy day. ;-)
Again thanks for testing, i realy apreasiate this,
kind regards,
Djek

armsys
Automation Wizard
Posts: 1108
Joined: Wed Dec 04, 2002 10:28 am
Location: Hong Kong

Post by armsys » Tue Nov 22, 2011 5:48 am

Djek
You don't have to torture yourself with install/uninstall.
Just run:
%ProgramFiles(x86)%\Macro Scheduler 12\msched.exe
%ProgramFiles(x86)%\Macro Scheduler 13\msched.exe

User avatar
Djek
Pro Scripter
Posts: 147
Joined: Sat Feb 05, 2005 11:35 pm
Location: Holland
Contact:

Post by Djek » Tue Nov 22, 2011 12:00 pm

FYI
Ok, I now installed V13.0.01 (previous was V13.0.0)

hate to bring the bad news, but V12 is oke,
and V13.0.01 is not workable so slow.

Must be something in my laptop. For now I leave it this way For later: i try an other laptop.

Thanks all for botthering !

armsys
Automation Wizard
Posts: 1108
Joined: Wed Dec 04, 2002 10:28 am
Location: Hong Kong

Post by armsys » Tue Nov 22, 2011 12:12 pm

Hi Djek,
Please check your firewall and antivirus settings.

User avatar
Djek
Pro Scripter
Posts: 147
Joined: Sat Feb 05, 2005 11:35 pm
Location: Holland
Contact:

Post by Djek » Tue Nov 22, 2011 2:00 pm

Thanks for the tip Armstrong,
completely disabled Microsoft security essentials
Disabled firewall
but No, even if I boot with F8 in the safe mode with network, (winXPpro)
the "lag" continious making me nuts.
Im sure that its something like you suggested, but if I find it, Ill let you know.
The watchlist folding isnt there on V12 so there I dont have problems.
kind regards
Djek

User avatar
Rain
Automation Wizard
Posts: 550
Joined: Tue Aug 09, 2005 5:02 pm
Contact:

Post by Rain » Tue Nov 22, 2011 5:39 pm

Boot up in safe mode and then debug the script. I always do that first, it lets me know if the problem is another program I'm running or the one I'm having problems with.

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts