Please do something ( even if it is small ) to help tune performance.

dave_cowden

For complex features, we simply have no reasonable tools to tune performance.

What I've been doing when I need to 'profile' is to put things into a huge loop, and then use a stopwatch. Very time consuming.

Of course profiling is a complex topic, and doing it right is not trivial. 

That said, any of the following  simple changes would be far better than nothing:

• print the current system time or time since epoc ( to millisecond resolution ) optionally in println
• print system time or time since epoc in debug
• add a function now() or System.currentTimeMillis() like in java to get the current time
• provide a timing function that will run code in a closure and return the execution time

None of these make a reliable profiler, and I get that.  But any of them would be a huge improvement, and far better than nothing.

lemon1324

I'd also be interested in this functionality as a step on the way to an actual profiling tool. That being said I see how people who write FeatureScript and also want a profiling capability are probably a small subset of users.

ilya_baran

We've got some profiling work planned soon, but I see the immediate need.  I will do something to make it easier for the next update.
@lemon1324  the subset of users who want a profiling capability is small, but very important to us -- you guys are making everyone else's Onshape experience better

dave_cowden

Awesome,Thanks! This will be super helpful!