pyret-lang icon indicating copy to clipboard operation
pyret-lang copied to clipboard

Published 20 hours ago • verified publisher icon brownplt

Better performance measuring infrastructure

Open jpolitz opened this issue 11 years ago • 6 comments

Opening an issue to track work on measuring performance of Pyret programs and the compiler. This includes three main metrics that I can think of:

  • Compiled code size
  • Speed of compiled code (especially common patterns)
  • Memory footprint of running code (especially memory leaks)

We've tried to make a lot of performance improvements mostly based on looking at Chrome devtools and our own hunches, and we should be able to start doing better at this to figure out what changes will give us the most improvement for our effort.

jpolitz avatar Jul 15 '14 14:07 jpolitz

There seems to have been a lot of work on this, from a number of directions. Still worth keeping open?

schanzer avatar Oct 07 '16 18:10 schanzer

I would keep this open! I'll probably do work in this space over winter break again.

awstlaur avatar Oct 07 '16 19:10 awstlaur

Referencing https://github.com/brownplt/pyret-lang/pull/1266, which seems related

schanzer avatar Nov 30 '17 00:11 schanzer

@jpolitz Is this still open?

schanzer avatar Mar 17 '20 03:03 schanzer

Poking @awstlaur and @jpolitz . Where do we stand on this?

schanzer avatar Aug 12 '20 18:08 schanzer

Poking @awstlaur and @jpolitz . Where do we stand on this?

Long time no talk! These days my priorities are elsewhere, plus I haven't been tracking the progress of Pyret

awstlaur avatar Aug 13 '20 12:08 awstlaur