Creating a production release with :cover information

Questions / Help
1

I’d like to run a release with a “cover” information compiled in, run the application for a few days to collect the cover info to identify dead code in a legacy codebase. Optionally, doing so could help see what are the hot code paths in the app.

I’m not familiar with :cover module of Erlang, but based on the OTP27 release notes, cover has became quite fast, so I’m willing to risk running an app with :cover-compiled modules on a production workload.

2 Likes
2

If you try this out I’d love to read about how it goes!

1 Like
3

And of course I forgot to add a question… :man_facepalming:

What would be the steps to build such a release with such info? Has anyone done anything like this and willing to share their experience?