Timeline for Remote database -> massive response time increase?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 8, 2023 at 11:16 | comment | added | Tom J Nowell♦ | In hindsight I should also have mentioned that if you have a database in the USA, and want to serve your site in New Zealand/Australia very quickly then that's not possible if you're connecting to a server in the USA, and that's not how big corporations do it, they replicate their database servers so that there are copies, and it's the copy/replicated/secondary database server that handles the request. Replication is a huge topic in and of itself, and there are lots of different strategies for doing it, e.g only handling writes in the USA DB server but reads are ok everywhere | |
| Apr 20, 2014 at 12:11 | vote | accept | no6 | ||
| Mar 31, 2014 at 22:59 | comment | added | Tom J Nowell♦ | In this particular scenario, a fast server in the US would be faster worldwide than what you currently have, aside form exceptions such as China. Switching CMS isn't going to make the SQL query latency vanish if you want fast loading times. Continuing down this avenue leads to server related questions, and that would be off topic on this site. I suggest you find a good Server person | |
| Mar 31, 2014 at 22:44 | vote | accept | no6 | ||
| Apr 20, 2014 at 12:11 | |||||
| Mar 31, 2014 at 22:43 | comment | added | no6 | Thank you, 1. "Considering that some setups can respond in full in less than 100ms never mind the database connection" How ? 2. Suppose you want to run WP on multiple geographical locations. What would you do ? Install DB server in each location and replicate between databases ? (Replication introduces new problem of data consistency) 3. Is there any other out-of-box web app similar to WP that can work with such latency ? (It does not have to be php+mysql based, even mongo+ruby) | |
| Mar 31, 2014 at 22:20 | history | answered | Tom J Nowell♦ | CC BY-SA 3.0 |