> If you don't think imposing a 2x slowdown on web apps is a showstopper > then clearly we have very different views on performance. (Note, using > your high estimate of two orders of magnitude it would be a 6x > slowdown if 5% of an application's time [not instructions] is spent in > floating point arithmetic.)
And if it were 1% in FP arithmetic and one order of magnitude, it would be a 1.1x (10%) slowdown. > From my point of view, this would be a massive regression and > conclusively rules out the idea of replacing binary floating point > with decimal floating point in ECMAScript. I too would like to see high performance and the correct results in calculations. And I would rather see correct results with slower performance than fast results with incorrect results. As a result of the latter, many apps are forced to go back to the server for 'business logic', which has a disastrous effect on response times to the user (but at least, on the server, apps now have the option of decimal FP hardware). But as you are more concerned with client-side performance, I think, can you show us a real script that spends anything like 5% of its time in floating-point arithmetic? I failed to create an artificial one that used as much as that (but that was a few years ago; today's ECMAScript engines might have different characteristics). Mike Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU _______________________________________________ Es4-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es4-discuss
