>> I think it would be vastly better for Firebird to address operating across >> cheap >> commodity servers than to optimize for exotic -- and hyper-expensive -- >> servers. > > Operating across servers is ... a cluster, which suggests MPI as the method > to distribute messages between the nodes... which is one of the areas/items > that I trying to speak to. > > But to start with, making changes to get the most out of the local resources > would seem a reasonable place to start. My 100+ clients rarely come close to > saturating CPU and/or disk IO (SSDs are making that more and more difficult). > Which tells me that the current approaches are not maximized.
+1. IMHO 99% of the Firebird customer-base isn't in the "distributed system business", thus state-of-the art scale up (instead of scale out) capabilities on a single server will be excellent. Firebird 3 is a first great step into that direction. Thomas ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
