Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Please do something ( even if it is small ) to help tune performance.
dave_cowden
Member, Developers Posts: 474 ✭✭✭
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:
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
0
Comments
PhD, Mechanical Engineering, Stanford University
@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