C
ChUIMonster
Guest
The "chattiness" of the client/server protocol makes it *very* sensitive to latency -- on localhost it's no big deal, a good fast LAN with sub-millisecond ping response times is also usually ok. Wi-fi tends to have a lot more latency and congestion issues than a wired LAN. Especially if it is heavily used. Configuring wi-fi in a high-usage environment is very difficult. A WAN can get really ugly -- especially if you get routed through a satellite link 
And the whole Meltdown/Specter thing is not helping either -- the two classes of applications most severely impacted are those that make a lot of system calls and those that do a lot of IO (which is a somewhat redundant statement since IO and system calls are inseparable...) A "chatty" networking protocol associated with a database is your classic "perfect storm"
Continue reading...
And the whole Meltdown/Specter thing is not helping either -- the two classes of applications most severely impacted are those that make a lot of system calls and those that do a lot of IO (which is a somewhat redundant statement since IO and system calls are inseparable...) A "chatty" networking protocol associated with a database is your classic "perfect storm" Continue reading...