How can SQL Relay improve the efficiency of my website?
Here are some examples of how SQL Relay can improve the efficiency of your web site. Let’s say you’re running CGI’s againt a transactional database such as PostgreSQL, MS SQL Server or Oracle. CGI’s have to log into and out of the database each time they run. If you use SQL Relay to maintain persistent connections to the database and just log into and out of SQL Relay, you can reduce the amount of time wasted establishing database connections and handle more CGI requests per-second. This is both because the time-cost of connecting to SQL Relay is smaller than the time-cost of connecting to a transactional database, and because the SQL Relay client library is smaller than most database client libraries, resulting in a more lightweight CGI. Let’s say you’re using Apache, PHP and Oracle and you determine by doing all sorts of analysis that you need to keep 30 Apache processes running to provide adequate response. Since most of your site isn’t database-driven, on average, no more than 5 PH
Related Questions
- Why doesn the last connection die off when I set connections=0 and maxconnections to some larger number and let SQL Relay go idle for a long time?
- If I set up SQL Relay to use dynamic scaling, it eventually spawns off as many connections as it can and they never die off. Whats up with that?
- How can SQL Relay improve the efficiency of my website?
