Comment #1 on issue 2741 by [email protected]: max_opt_count is
implemented using the wrong kind of limit
http://code.google.com/p/v8/issues/detail?id=2741
Here's an example of how Octane's numbers change in such a weird way, and
why I've suggested making that value a weight for how aggressive chrome
should compile, not some unrespected(overhead causing) limit.
--max_opt_count=1 => pdf.js: 15945 CodeLoad: 12892
--max_opt_count=10 (Default) => pdf.js: 16234 CodeLoad: 13219
--max_opt_count=20 => pdf.js: 17464 CodeLoad: 13658
--max_opt_count=50 => pdf.js: 15945 CodeLoad: 13456
--max_opt_count=100 => pdf.js: 15285 CodeLoad: 13165
--max_opt_count=200 => pdf.js: 7767 CodeLoad: 12595
--max_opt_count=500 => pdf.js: 7476 CodeLoad: 13050
--max_opt_count=1000 => pdf.js: 1563 CodeLoad: 13395
--nocrankshaft => pdf.js: 13353 CodeLoad: 13841 (was getting
15k on this yesterday so this seems to be influenced by other external
factors)
But if you really don't/can't find a way to make it a range based
compilation heuristic, I'll suggest you up the value to 20-25 :P
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
