Hmm. In my experience running binaries compiled with ---enable-debug do have a noticeable performance degradation. Not nearly as bad as turning on debug tags, but quite noticeably when looking at peers running non-debug-enabled binaries.
So might be adequate to run on a few machines to catch problems (like ASAN builds), but probably not how you want to build your standard production binaries. On Tue, Apr 20, 2021 at 4:19 PM Sudheer Vinukonda <sudheervinuko...@yahoo.com.invalid> wrote: > Hmm, I have not really stress tested in particular with the binary > compiled using '-enable-debug', but have definitely used such a binary in > production with not much of a noticeable degradation (if any). The one > benefit in using such a binary is that it enables debug asserts > (ink_assert) and allows to catch potential bugs that only crash in non > release builds. Of course, the risk in deploying such a binary in all of > your production is a potential systematic crash across the entire set of > ATS boxes, but, I've definitely used and deployed such build in a small > number of hosts in the past. > Thanks, > Sudheer > On Tuesday, April 20, 2021, 02:12:57 PM PDT, Chou, Peter < > pbc...@labs.att.com> wrote: > > Hi, > > I know there was some discussion on the bug scrub (last week I think) that > enabling debug output in the records.config on any debug tags will greatly > reduce performance. > > Is it also the case that using a binary compiled with '-enable-debug' will > also cause performance issues? > > Thanks, > Peter >
