On May 23, 2017, at 1:43 PM, Jay Pipes <jaypi...@gmail.com> wrote: > [1] Witness the join constructs in Golang in Kubernetes as they work around > etcd not being a relational data store:
Maybe it’s just me, but I found that Go code more understandable than some of the SQL we are using in the placement engine. :) I assume that the SQL in a relational engine is faster than the same thing in code, but is that difference significant? For extremely large data sets I think that the database processing may be rate limiting, but is that the case here? Sometimes it seems that we are overly obsessed with optimizing data handling when the amount of data is relatively small. A few million records should be fast enough using just about anything. -- Ed Leafe __________________________________________________________________________ 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
