3 ms·
We usually wrap a set of valgrind debugged small test/demo programs that hammer a library to monitor for leaks etc. However, ensuring thread safety can sometim
by Joel_Mckay 3y ago
We usually wrap a set of valgrind debugged small test/demo programs that hammer a library to monitor for leaks etc.
However, ensuring thread safety can sometimes be a challenge. =)
- inetknght 3y agoWe run unit tests with ASAN. Good test coverage gives us good confidence in safety. I recently picked up a subscription to undo.io and I figure the next time I see any problem then I'll take that for a spin. I've seen trouble with gRPC and trying to debug it is infuriating.
- Joel_Mckay 3y agoI just used AMQP routing to handle loads, and small limited-run programs that cache credentials like netflix biological inspired systems. We were never convinced gRPC could efficiently handle the periodic traffic spike-nature of our data streams (more of n! edges in fault tolerant mode concern). i.e. we run our intake like an insect colony to handle the various architecture roles, and each process instance is only handling a few network links at a time (i.e. gets rid of threading cleanup, busy credential store hits, and error routing.) I wish they used Erlang/Elixir/Phoenix channels to reduce the system complexity, https://dev.to/codecast/how-to-use-phoenix-channels-18k9 https://dev.to/codecast/how-to-use-phoenix-channels-18k9 Sometimes we just need to keep a system running, and quietly replace it with version 2 later... Yet later usually never arrives... lol =)