Reply to thread

Message

<blockquote data-quote="Janx" data-source="post: 1839095" data-attributes="member: 8835">As a note on a box I run, it goes full throttle anytime there's a page request.&nbsp; The rest of the time it sits idle.&nbsp; The gist is, Linux will devote as much processor as a process needs, barring other demands for attention.&nbsp; So it's very easy for a process to show a high utilization rate initially.&nbsp; Once those hits keep coming in steady streams, things would start balancing out.I agree that you should go SCSI RAID if you can.&nbsp; You could still do well with ATA/SATA, but make sure you do some kind of hardware based RAID and not OS mirroring.Double check your use of PHP.&nbsp; I could have sworn they had a precompiling cache thingy called ZEND built in.&nbsp; I've been working with ASP.net lately, so I might be a bit stale.Also, the latest MySQL (v5) is coming out with some SQL caching stuff that could speed up some common queries.Use CHAR instead of VARCHAR if you can, that got a lot of speed back in one of our apps.Stick with Linux.&nbsp; PHP and MySQL are best in that environment.&nbsp; We actually just switched one of our servers from Windows to linux (same PHP and MySQL) and got some more performance back.If you do 2 servers, 1 DB and 1 web server, run a dedicated private network between the 2.&nbsp; A 1Gb cross-over wire might be sufficient.&nbsp; By having the two communicate over the private network, you'll relieve the bottleneck of web server to DB.&nbsp; Naturally, you'd have the biggest channel for the 2 if they were on the same server.&nbsp; But if both processes are vying for CPU, then splitting them up but giving them as big a pipe as you can will help things.Janx</blockquote>

[QUOTE="Janx, post: 1839095, member: 8835"] As a note on a box I run, it goes full throttle anytime there's a page request. The rest of the time it sits idle. The gist is, Linux will devote as much processor as a process needs, barring other demands for attention. So it's very easy for a process to show a high utilization rate initially. Once those hits keep coming in steady streams, things would start balancing out. I agree that you should go SCSI RAID if you can. You could still do well with ATA/SATA, but make sure you do some kind of hardware based RAID and not OS mirroring. Double check your use of PHP. I could have sworn they had a precompiling cache thingy called ZEND built in. I've been working with ASP.net lately, so I might be a bit stale. Also, the latest MySQL (v5) is coming out with some SQL caching stuff that could speed up some common queries. Use CHAR instead of VARCHAR if you can, that got a lot of speed back in one of our apps. Stick with Linux. PHP and MySQL are best in that environment. We actually just switched one of our servers from Windows to linux (same PHP and MySQL) and got some more performance back. If you do 2 servers, 1 DB and 1 web server, run a dedicated private network between the 2. A 1Gb cross-over wire might be sufficient. By having the two communicate over the private network, you'll relieve the bottleneck of web server to DB. Naturally, you'd have the biggest channel for the 2 if they were on the same server. But if both processes are vying for CPU, then splitting them up but giving them as big a pipe as you can will help things. Janx [/QUOTE]

Verification