Thread: Web & DB Servers
I'm wondering what the better solution is: Apache/PHP & PgSQL on one physical server with 100% performance (ie. 1200 MHz, 2GB RAM) or have Apache & PgSQL each on a server with half the performance (600MHz/1GB RAM each). I'm especially curious in the way long running queries affect the L2 cache performance in the mixed enviroment. What if Apache & PgSQL are fighting over the L2 cache making it's large size (in case of the new .13 micron CPU's from Intel) rather useless compared to the "dedicated solution", where each CPU runs only one application and can use the cache better? Maybe I'm missing something here completely, so I would appreciate any comments/suggestions. Is there a noticable performance gain in splitting the server in two? Thanks! -Zavier
It depends on what you are doing...I have a stripped down server that is apache & pgsql with nothing else. It is a 933mhz with 256M ram and I have optimized both apache and pgsql to run. I have really nothing else on the system. The only draw back I see is that if you split the two up and you have tons of network traffic; you queries might take longer over the network. You also have the question of authentication with pgsql for the connection when you have the two on different machines. If you trust you network 100% then you can have a trusted connection--else you need to set up some type of authentication which might decrease performance. I have not done any testing in this area; however, I am debting whether or not to go down the road.
As for the cpu's, I have not looked into the L2 cache as of yet.
Hope this helps...
Ray Hunter
Firmware Engineer
ENTERASYS NETWORKS
-----Original Message-----
From: Zavier [mailto:zavier@zavier.net]
Sent: Friday, February 08, 2002 7:03 PM
To: pgsql-php@postgresql.org
Subject: [PHP] Web & DB Servers
I'm wondering what the better solution is:
Apache/PHP & PgSQL on one physical server with 100% performance (ie. 1200 MHz, 2GB RAM) or have Apache & PgSQL each on a server with half the performance (600MHz/1GB RAM each).
I'm especially curious in the way long running queries affect the L2 cache performance in the mixed enviroment. What if Apache & PgSQL are fighting over the L2 cache making it's large size (in case of the new .13 micron CPU's from Intel) rather useless compared to the "dedicated solution", where each CPU runs only one application and can use the cache better? Maybe I'm missing something here completely, so I would appreciate any comments/suggestions. Is there a noticable performance gain in splitting the server in two?
Thanks!
-Zavier
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
RE: [PHP] Web & DB Servers I'm not an apache techman, but 1GB RAM to an apache installation isn't overestimated? You may think about a SMP box with two processors, too. If you are thinking on how to achive better performance you must take into account that database tasks are more or less disk intensive stuffs. You should consider rather to set up a fast hard disk environment. BTW, having much memory is really a good choice. You may try to read Bruce Momijam's column about database performance tips. I think it is listed on the techdoc site: http://techdocs.postgresql.org (i found the exact url: http://www.ca.postgresql.org/docs/hw_performance or http://candle.pha.pa.us/main/writings/pgsql/hw_performance/index.html ) (also search postgresql-general mailing list archive, similar questions and discussions always rise up there, too : http://marc.theaimsgroup.com/?l=postgresql-general&r=1&w=2) IMHO, using authentication is really needed in any production site, no matter if database and other application is sitting on the same machine or not. ----- Original Message ----- From: Hunter, Ray To: 'Zavier' Cc: pgsql-php@postgresql.org Sent: Monday, February 11, 2002 2:36 PM Subject: Re: [PHP] Web & DB Servers It depends on what you are doing...I have a stripped down server that is apache & pgsql with nothing else. It is a 933mhzwith 256M ram and I have optimized both apache and pgsql to run. I have really nothing else on the system. The onlydraw back I see is that if you split the two up and you have tons of network traffic; you queries might take longer overthe network. You also have the question of authentication with pgsql for the connection when you have the two on differentmachines. If you trust you network 100% then you can have a trusted connection--else you need to set up some typeof authentication which might decrease performance. I have not done any testing in this area; however, I am debtingwhether or not to go down the road. As for the cpu's, I have not looked into the L2 cache as of yet. Hope this helps... Ray Hunter Firmware Engineer ENTERASYS NETWORKS -----Original Message----- From: Zavier [mailto:zavier@zavier.net] Sent: Friday, February 08, 2002 7:03 PM To: pgsql-php@postgresql.org Subject: [PHP] Web & DB Servers I'm wondering what the better solution is: Apache/PHP & PgSQL on one physical server with 100% performance (ie. 1200 MHz, 2GB RAM) or have Apache & PgSQL each on aserver with half the performance (600MHz/1GB RAM each). I'm especially curious in the way long running queries affect the L2 cache performance in the mixed enviroment. What if Apache& PgSQL are fighting over the L2 cache making it's large size (in case of the new .13 micron CPU's from Intel) ratheruseless compared to the "dedicated solution", where each CPU runs only one application and can use the cache better?Maybe I'm missing something here completely, so I would appreciate any comments/suggestions. Is there a noticableperformance gain in splitting the server in two? Thanks! -Zavier ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
Here's a tip for more performance. Use Apache only for .php files and use 'thttpd' for all static content. thttpd beats the pants off Apache for static content. Chris -----Original Message----- From: pgsql-php-owner@postgresql.org [mailto:pgsql-php-owner@postgresql.org]On Behalf Of Hunter, Ray Sent: Monday, 11 February 2002 9:37 PM To: 'Zavier' Cc: pgsql-php@postgresql.org Subject: Re: [PHP] Web & DB Servers It depends on what you are doing...I have a stripped down server that is apache & pgsql with nothing else. It is a 933mhz with 256M ram and I have optimized both apache and pgsql to run. I have really nothing else on the system. The only draw back I see is that if you split the two up and you have tons of network traffic; you queries might take longer over the network. You also have the question of authentication with pgsql for the connection when you have the two on different machines. If you trust you network 100% then you can have a trusted connection--else you need to set up some type of authentication which might decrease performance. I have not done any testing in this area; however, I am debting whether or not to go down the road. As for the cpu's, I have not looked into the L2 cache as of yet. Hope this helps... Ray Hunter Firmware Engineer ENTERASYS NETWORKS -----Original Message----- From: Zavier [mailto:zavier@zavier.net] Sent: Friday, February 08, 2002 7:03 PM To: pgsql-php@postgresql.org Subject: [PHP] Web & DB Servers I'm wondering what the better solution is: Apache/PHP & PgSQL on one physical server with 100% performance (ie. 1200 MHz, 2GB RAM) or have Apache & PgSQL each on a server with half the performance (600MHz/1GB RAM each). I'm especially curious in the way long running queries affect the L2 cache performance in the mixed enviroment. What if Apache & PgSQL are fighting over the L2 cache making it's large size (in case of the new .13 micron CPU's from Intel) rather useless compared to the "dedicated solution", where each CPU runs only one application and can use the cache better? Maybe I'm missing something here completely, so I would appreciate any comments/suggestions. Is there a noticable performance gain in splitting the server in two? Thanks! -Zavier ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
Thanks to all who replied. I think I'll go with an SMP box as it is less maintenance than two separate boxes... >IMHO, using authentication is really needed in any production site, no matter >if database and other application is sitting on the same machine or not. I agree. -Zavier _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com