On 10 May 2016 at 06:58, Hayes, Graham <graham.ha...@hpe.com> wrote: > From a deck about "the rise and fall of Bind 10" [0] - > > "Python is awesome, but too damn slow for DNS"
That slide deck doesn't provide any analysis on *what* that means - latency? requests per second? Dollars-per-millions-requests-per-second? https://github.com/bundy-dns/bundy/blob/master/src/lib/python/bundy/server_common/bundy_server.py <- they wrote their server around select(), which has been pretty much deprecated for high performance - whether scale or latency (except with very small connection counts) servers for decades... tl;dr: I don't trust their ability to make the statement that Python is too slow, because their code is failing a basic sniff test in this space. A UDP only DNS server could get away with select (in fact, it might possibly be optimal), but something handling TCP will rapidly run into terrible scaling problems - quadratic overheads - with select. -Rob -- Robert Collins <rbtcoll...@hpe.com> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
