Two general approaches, where both run the garbage collector before timing or
profiling:
1) basic timing information;
gc [ foo ] time
(or if the word is slow, run it a few times)
gc [ 1,000 [ foo ] times ] time
2) profiling
gc [ foo ] profile
This saves the profile, allowing you to view it various ways:
top-down profile.
top-down-max-depth profile.
flat profile.
Etc
On May 27, 2013, at 10:19 AM, Gabriel Kerneis <[email protected]> wrote:
> On Mon, May 27, 2013 at 09:51:04AM -0700, John Benediktsson wrote:
>> Nice! Have you had a chance to look at performance?
>
> Not yet, but this is on my TODO list. I'm working on ECB and CBC modes, so
> it's
> probably worth finishing that first and then test with large files.
>
> Is there any recommanded way to benchmark execution time (or performance in
> general) in Factor?
>
> Best regards,
> --
> Gabriel
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Factor-talk mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/factor-talk
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk
