Frequently Asked Questions

Estimated reading time: 8 mins

Last edited: 27 Oct 2020

  • RevDeBug does not inspect everything the Virtual Machine is processing, but only parts that were instrumented beforehand. Which allows fine-tuning of what you record and what slowdown you can expect.

    There are two main recording modes - Crash Recorder and Live Recorder.

    • Crash recorder performs really well in the production environment for constant monitoring of your applications and bug reporting. It will send the last N amount of steps the application took before crashing. (it does not matter if you have 1, 5 or 10.000 applications deployed) the performance overhead you can expect is around ~5%.
    • The Live Recorder records everything that happens in your application without the limitation of steps back you can take and sends it on the go to your recording server. If there is a lot of data manipulation taking place in memory, recording such data to disk, which RevDeBug does, will make your application run slower. Average slowdown we have observed is between 40% to 7 times.

    Below are results of running unit testing suites of various Open Source projects to give you overall feel about performance penalty:

    NInject (dependency injection framework)
    HearthstoneDeckTracker (WPF desktop app)
    SocialGoal (MVC 5 Web app)