samcrawford

22 ms·

211.
by samcrawford 13y ago
This is not terribly uncommon (although not widely talked about). It'll almost certainly be a Google Global Cache setup ( https://peering.google.com/about/ggc.html ). You might find it's Google, not BT, that is
212.
by samcrawford 13y ago
I suspect it's based upon this SBC (given it's from the same company and this SBC is marked as a new product): http://compulab.co.il/products/computer-on-modules/cm-fx6/#o... This should give some r
213.
by samcrawford 13y ago
It would be helpful if the author included the round-trip latency (even some simple pings) alongside the benchmark so we could judge how far the servers are from the client. This will have a significant impact on the ab numbers (particularl
214.
by samcrawford 13y ago
I disagree that any serious installation is using innodb_file_per_table. It does have downsides. In our use case we're making very heavy usage of table partitioning (over 500 partitions for some of our very large tables). Because each
215.
by samcrawford 13y ago
For me, this was a really unsatisfying answer. Maybe the question should have been more specific, but I took it to relate to the PRISM programme and the specific technology that provided direct access to data at the companies involved. His
216.
by samcrawford 14y ago
I too joined Lehman as a graduate in 2007. My experience was different; I was based in the London office and was in a back-office role (IT Infrastructure). I also worked there as an intern in 2005-2006 (or "Industrial Placement" in Lehman-s