profiling

Join us Thursday, November 20th, 5:00 PM - 6:00 PM GMT (check other zones) for a free webinar, Taking Advantage of PhpStorm IDE
 and Zend Server Integration with Mikhail Vink and Joshua Solomin. Write code with pleasure and make sure that your project is safely deployed and easy to debug, with the new collaboration between JetBrains and Zend! During this webinar we’ll explore the integration between Zend Server’s Z-Ray and the PhpStorm IDE, from debugging and profiling your applications seamlessly to preparing deployment packages in the IDE to be deployed to Zend Server, and more. Mikhai

Forget about the NSA: PhpStorm 8 EAP comes with spy-js, our own secret service that allows tracing our code without console.log, debugging it without breakpoints and profiling it without any specialized tools. All while running our web app (and even other web apps out there on the Internet, it's a secret service after all). Sounds like some serious espionage, right? Let's have a quick look at what it can do for us. A picture is worth a thousand words, and a moving picture is worth ten times that. So here's a 7-minute introduction video to spy-js: https://www.youtube.com/watch?v=vPIbwxzC5

That application we are building is way too slow. What gives? Did someone on our team commit code while partying? Are we making too many database calls? The only way to learn about the performance of our application code is to profile it. Something that's fairly easy to do with PhpStorm! Whether it's a full web application, some library code or just a unit test, profiling allows us to gather program execution statistics. Information like the names of functions executed, the number of times a function has been executed, how long a function took to execute and such can give us a hint on