PRFLR, or how your code works in production
Colleagues, welcome. We want to tell you about our project called PRFLR. This is a tool for analyzing the performance of the code directly in production mode. And realtime.
What is production? This is when you analyze the work of your live work applications on servers, devices, work computers. Those. Get real life data on applications, not synthetic ones.
Realtime? This means that if a user clicks a button in an application, then the data will be available to you after 1 second.
')
Performance Analysis?
Here it is worth telling in more detail. Programmers have utilities for tracing code, debuggers are there, there are log aggregation systems. But until now there was no tool that would allow collecting statistics on the execution time of an arbitrary piece of code, build a distribution, show min / avr / max, the number of calls and total machine time spent on executing this code. PRFLR is just such a tool. It accumulates data for a certain period of time of the application and allows you to make different cuts analytics, comparing the performance of different parts of the code, sort them by various parameters and look for bottlenecks in the code that inhibit the application. And PRFLR is doing quite well with this single task.
We use this service for 9 of our projects, and decided to provide it to the developer community. At the moment, the service is completely free and will remain so for most users. However, especially large users, we will eventually ask to share the burden of paying for the server infrastructure.
Interested? To try PRFLR in work, you need to take a few steps:
What is production? This is when you analyze the work of your live work applications on servers, devices, work computers. Those. Get real life data on applications, not synthetic ones.
Realtime? This means that if a user clicks a button in an application, then the data will be available to you after 1 second.
')
Performance Analysis?
Here it is worth telling in more detail. Programmers have utilities for tracing code, debuggers are there, there are log aggregation systems. But until now there was no tool that would allow collecting statistics on the execution time of an arbitrary piece of code, build a distribution, show min / avr / max, the number of calls and total machine time spent on executing this code. PRFLR is just such a tool. It accumulates data for a certain period of time of the application and allows you to make different cuts analytics, comparing the performance of different parts of the code, sort them by various parameters and look for bottlenecks in the code that inhibit the application. And PRFLR is doing quite well with this single task.
We use this service for 9 of our projects, and decided to provide it to the developer community. At the moment, the service is completely free and will remain so for most users. However, especially large users, we will eventually ask to share the burden of paying for the server infrastructure.
Interested? To try PRFLR in work, you need to take a few steps:
- Sign up at prflr.org and get the API KEY
- Download SDK ( #, C +, Java, PHP, Perl, Python, Go, Node.js) github.com/PRFLR
- Integrate the SDK and set the timers in the code.
- Roll out your application to production and see analytics.
Source: https://habr.com/ru/post/213281/
All Articles