Book Image

TypeScript High Performance

By : Ajinkya Kher
Book Image

TypeScript High Performance

By: Ajinkya Kher

Overview of this book

<p>In a world where a tiny decrease in frames per second impacts customer engagement greatly, writing highly scalable code is more of a necessity than a luxury. Using TypeScript you get type checking during development. This gives you the power to write optimized code quickly. This book is also a solid tool to those who’re curious to understand the impact of performance in production, and it is of the greatest aid to the proactive developers who like to be cognizant of and avoid the classic pitfalls while coding.</p> <p>The book will starts with explaining the efficient implementation of basic data Structures, data types, and flow control. You will then learn efficient use of advanced language constructs and asynchronous programming. Further, you'll learn different configurations available with TSLint to improve code quality and performance. Next, we'll introduce you to the concepts of profiling and then we deep dive into profiling JS with several tools such as firebug, chrome, fiddler. Finally, you'll learn techniques to build and deploy real world large scale TypeScript applications.</p>
Table of Contents (17 chapters)
Title Page
Credits
Foreword
About the Author
Acknowlegement
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
7
Profile Deployed JS with Developer Tools and Fiddler

Chrome Developer Tools


Chrome Developer Tools is a great utility at the disposal of developers, right from writing code and debugging it locally, to monitoring deployed code on the server. Let's explore the different ways in which we can profile our deployed JavaScript code.

Memory profiling

Let's take a look at how we can perform memory profiling using Chrome Developer Tools.

Recollect our string concatenation example from Chapter 1, Efficient Implementation of Basic Data Structures and Algorithms where we compared the concat  operator versus the += operator as two ways to perform concatenation. The resultant string was the same in both cases, but, if you remember, one method resulted in a memory explosion. Let's try to look at how we could have caught this with the Chrome Developer Tools memory profiler.

Note

You can open the developer tools on Chrome by hitting CMD+SHIFT+I on a Mac or CTRL+SHIFT+I on a PC. On the Dev Tools there are several tabs, each of them serving a specific purpose. The...