Call it "several" times (where "several" is enough to make it take a
significant amount of time) and measure the time it's taken to execute.
Obviously this is somewhat easier for idempotent methods than ones
which alter state and need to be "reset".
With a normal method you than mostly do not even see it in ticks (1/1000
second)
However mostly it is just try and see what is in your method, when you are
doing datahandling or much screen refreshing, it takes some time. Mostly is
even complex text handling very fast when you use the right
functions/methods.
That depends - is it rendering a complex 3D model on a large area, or
is it checking whether you passed it true or false?
Without knowing what the method is meant to achieve, there's no way on
earth of knowing what constitutes "performing well".
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
