<commit_before>Saving Money and Delighting Customers with Faster JavaScript
================================================================================

Are you interested in saving money and delighting customers?  One way to do this is to find out where your application is slow, and then making those slow parts fast.  For your server code, removing slow code will save you money, since your applications will use less processor time.  For your server and browser code, your customers will be happier with applications that are snappier.

Developers often take guesses at where they think the slow code is in an application, or use crude timing tools to collect data on performance.  But there's no need to guess or use crude tools!  JavaScript environments for the browser and Node.js include CPU profiling tools which can identify which parts of your JavaScript code are slow.  This provides crucial insight on where you can speed them up.  In this talk you'll find out what CPU profiling tools are, what tools are available, and show a brief demo of how they are used.<commit_msg>finally commit final changes to proposal; was not accepted<commit_after>Saving Customers and Money by Making It Go Faster
================================================================================

Your application's performance is key to keeping customers happy and reining in hardware costs.  Customers frustrated with slow applications just stop using them.  Poorly performing applications require more machines to run them, compared to optimized applications.

In order to fix poor performance problems, you first have to identify them.  For many programming environments, this involves using specialized tools and environments and sometimes experts, to analyze the application.  For JavaScript, we are fortunate to have CPU profiling tools baked right into the JavaScript runtimes, allowing every developer to do performance analysis.

In this talk we'll go over profiling tools available for Node.js and the browser.  We'll show a brief demo of how these tools can be used to find the slow code in an application, at both development time and in production.
{'fraction_non_alphanumeric': 0.09495136637332098, 'fraction_numerical': 0.0, 'mean_word_length': 5.189111747851003, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6255470', 'n_tokens_mistral': 439, 'n_tokens_neox': 413, 'n_words': 313}