Proxy performance: JIT-compilation?
ajvincent at gmail.com
Fri Aug 4 23:30:55 UTC 2017
So, how many boxes of chocolates do I need to send to the two big vendors
in Mountain View? :-)
It's been fifteen years since I seriously tried to profile C++ code, and I
didn't really know what I was doing back then: unfamiliar tools, and less
competence in C++ than I would've liked. What little knowledge of
profiling I had back then has long since faded.
Even if I could generate a pretty picture of how long we spent in each code
path, I wouldn't know how to interpret it.
I recently submitted a patch for improving error reporting in SpiderMonkey
, so I can occasionally dip my toes in the JSAPI code...
On Fri, Aug 4, 2017 at 2:52 PM, Allen Wirfs-Brock <allen at wirfs-brock.com>
> I don’t think the barriers to such optimization are technical. It’s more
> a matter of convincing that engine implementors that doing the work
> (probably significant) to optimizing Proxies in this manner is a sound
> investment and hight priority
"The first step in confirming there is a bug in someone else's work is
confirming there are no bugs in your own."
-- Alexander J. Vincent, June 30, 2001
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss