As you’ve seen, ASSERTs are not compiled into production images. There are far too many of them to simply change the macro in CLIB_DEBUG=0 images and expect anything like acceptable performance.
I would guess it’s at least a 50% hit. A -g -O0 (TAG=vpp_debug) image is often an order-of-magnitude slower than a production image for a given use-case. When I decide that an error condition warrants checking in production images, I generally use a clib_warning(...); abort(); pair. There’s no point in submitting a patch which changes the ASSERT macro, it will not be merged. D. From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of chetan bhasin Sent: Friday, June 15, 2018 5:11 AM To: vpp-dev@lists.fd.io Subject: [vpp-dev] How to disable assert in VPP Hi , For deployment , we want to replace assert with error log. Is there a way in VPP to do that? Thanks, Chetan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9627): https://lists.fd.io/g/vpp-dev/message/9627 Mute This Topic: https://lists.fd.io/mt/22293940/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
