Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Firefox Developers Continue Tuning ASM.js Performance

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,906

    Default Firefox Developers Continue Tuning ASM.js Performance

    Phoronix: Firefox Developers Continue Tuning ASM.js Performance

    Mozilla developers continue to optimize everything they can with ASM.js to deliver the greatest performance possible inside Firefox...

    http://www.phoronix.com/vr.php?view=MTU1MDM

  2. #2
    Join Date
    Sep 2010
    Posts
    467

    Default

    Responsibity matters sometimes more than performance.

    Seriously the responsivity issues are more pressing than the perofrmance of ASM.js is now.

  3. #3
    Join Date
    Jan 2013
    Posts
    159

    Default

    Quote Originally Posted by plonoma View Post
    Responsibity matters sometimes more than performance.

    Seriously the responsivity issues are more pressing than the perofrmance of ASM.js is now.
    Your forgetting asm.js is extremely useful for the low end device powered by FirefoxOS, has all the application on it, are web application.

  4. #4
    Join Date
    Oct 2011
    Location
    Germany
    Posts
    239

    Default

    Quote Originally Posted by iniudan View Post
    Your forgetting asm.js is extremely useful for the low end device powered by FirefoxOS, has all the application on it, are web application.
    you WASTE 50% speed on an already low powered device?

  5. #5
    Join Date
    Jan 2013
    Posts
    159

    Default

    Quote Originally Posted by Thaodan View Post
    you WASTE 50% speed on an already low powered device?
    FirefoxOS application are intended to be universal, so web application make sense and it doesn't mean that software aren't running locally, just that they use web standard.

  6. #6
    Join Date
    Mar 2009
    Posts
    159

    Default

    Quote Originally Posted by Thaodan View Post
    you WASTE 50% speed on an already low powered device?
    Explain please.

  7. #7
    Join Date
    Jan 2011
    Posts
    1,287

    Default

    Quote Originally Posted by Thaodan View Post
    you WASTE 50% speed on an already low powered device?
    Chill out. Even though I'd prefer native code, specially in resource constrained environments as mobile, that's currently the norm. Scripted/JIT languages provide some conveniences apps developers want, such as not having to test in every platform out there (portability). The only ones not using this kind of resource wasting (well, some resources, one could argue there is a very important resource which is more efficiently used with those languages, the developer's time) are Apple. Android runs the apps in a Java VM called Dalvik, for example. WinRT, AFAIK, uses .NET, which is managed and pretty much similar to JVM.

    Quote Originally Posted by Ferdinand View Post
    Explain please.
    It runs at around 50-75% the speed of native code, so the OP feels it's wasting that 50-25%.

  8. #8
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,128

    Default

    MS's own apps for WinPhone were almost all C++, and for WP8+ they graciously allowed non-MS developers too to use native languages. We must bow our heads, for this gift of fire is entirely wasted on our lowly selves. Afterall, weren't we already speechless in our gratitude for being allowed to use an incomplete and slow .Net implementation?

    Note that winRT != winPhone.

  9. #9
    Join Date
    Sep 2011
    Posts
    64

    Default

    Quote Originally Posted by plonoma View Post
    Responsibity matters sometimes more than performance.

    Seriously the responsivity issues are more pressing than the perofrmance of ASM.js is now.
    faster means more responsive anyway. task finishes faster means less time locking up.
    only way to fix responsivity issues with poorly made js is multiprocess which they also work on

  10. #10
    Join Date
    May 2012
    Posts
    828

    Default

    Quote Originally Posted by balouba View Post
    faster means more responsive anyway. task finishes faster means less time locking up.
    only way to fix responsivity issues with poorly made js is multiprocess which they also work on
    Asm.js isn't meant to be used by hand, it's too low level, it only solves the performance issue of porting certain apps from native languages.
    It's not a cure, it's a painkiller, and hence has limited future and also widely depends on how Dart is gonna do.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •