• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Performance in SPAs

 
Ranch Hand
Posts: 167
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Michael and Josh,

Thanks for your new book and congratulations.

During development of a SPA, we usually focus on mockups, application logic, payload structure and business functionality. As we implement a new module, view, new feature of our SPA, we use variables, make DOM manipulations, add listeners to elements etc. which means increasing memory usage on client.
So if we ignore performance considerations during development, it is possile to come to a point that our app blows up browser's memory usage and our app responds very slow to events or even becomes non-responsive.
What would you suggest for performance considerations during development? Any tools to monitor / improve our apps mem usage? Or some patterns / anti-patterns that we need to think about?

Thanks in advance
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic