PRIMALScript 2011 - Timing and Debugging VBScript

[drlandau]

You can run scripts within the debugger, which is great.But is there any way to have PRIMALScript time each statement in the script, so you can easily spot which statements is the ones that you should try to optimize for faster execution?I'm thinking something along the line, that PRIMALScript would:- Time how long each line in the script (in milliseconds) takes to execute when running the script.- Afterwards show a list of the entire script execution history with all lines that have been executed listed in order of execution with the timestamp + the time spend since the previous line (so you can see which lines has used the most milliseconds).- Also show the cumulative time used for all the lines within each function (or other defined section) for each seperat run (if the functions are called many times)- And also the total time used for each function (the time consumed for all the times the function was called, put together in a total). This will greatly aid in determining which functions it makes most sense to try to optimize.Is that possible in 2011 - or is it something you have considered (or will consider)...?Thanks!Best regards,Nicolaj Rasmussen

[Alexander Riedel]

What you are describing is called a "Profiler". We have toyed with the idea but have not made any plans to implement this.
I'll try to create a blog post about that after the 2011 release to see how the response to something like that is.
Please feel free to remind me if you don't see anything within a reasonable amount of time after the 2011 release.

[drlandau]

That sounds great, thanks for the info.
I haven't been able to find any VBScript performance profilers, only some for ASP and JavaScript, so without knowing, I would expect interest to be high, especially if you can make a generic profiler that supports multiple languages. It is hard - or at least very tedious - to track down performance issues in scripts where you either have may lines of code - or the same lines gets called many times over, since you have to inject many lines of debugging to catch it (at least I don't know of any better ways

[FrankAndrew]

I agree!
This is the BEST way to optimize ANY script.

This should help everyone to write better code and give them another GREAT reason to use PrimalScript!

I will be looking forward to this feature.

[Alexander Riedel]

Thanks for that additional input Frank. I'll check what we can do.