 |
 |
 |
 |
#266290 - 01/07/04 06:03 PM
Re: UBBThreads Server Hardware Specs
[Re: Arwen]
|
Admin Emeritus
Resident Code Hacker
Registered: 01/09/00
Posts: 5438
Loc: Lynnwood, WA
|
Mmm. The board has about 300,000 messages. <br /><br />I'm hosting a Threads with ~400,000 messages on a single P4 2.0Ghz with 1.5 gigs of memory, and a single 7200 RPM IDE drive. <br /><br />We get about 120,000 new messages posted every month (~4,000 a day), with ~4 million monthly script pageviews. The database is kept pruned to its current size to prevent killing the server... load averages around 4-6 during peak hours. <br /><br />It isn't screaming fast all the time, but it isn't slow enough for anyone to complain. A PHP accelerator is a key part of keeping the server happy.<br /><br />Now, let's put things in perspective. While the database sizes are nearly the same, there are "only" ~300 new posts in the past 24 hours on the board, and "only" 100 people online in a 10 minute window. <br /><br />The board and MySQL should be quite happy on similar commodity hardware and lots of memory. 2 gigs or so. You can probably put together an 'entry-level' ~2GHz system for $500 or so that could later be expanded to use a faster processor or SCSI drives if the need is present. <br /><br />The key thing is going to be the memory for MySQL. The more memory it can use, the less it will have to go do disk. The less it goes to disk, the faster things perform. <br /><br />As a general rule, of course.
_________________________
UBB.classic: Love it or hate it, it was mine.
|
|
Top
|
|
|
|
 |
 |
 |
 |
 |
 |
 |
 |
#266297 - 02/27/04 05:28 PM
Re: UBBThreads Server Hardware Specs
[Re: bisbell]
|
Admin Emeritus
Resident Code Hacker
Registered: 01/09/00
Posts: 5438
Loc: Lynnwood, WA
|
Sure.<br /><br />PHP, like most modern scripting languages (Perl, Python, etc), uses a variant on a virtual machine, like Java and MS's .NET.<br /><br />When you visit a PHP script, PHP will parse the script, turn it into bytecode, then run the bytecode on its own internal engine.<br /><br />Bytecode caches intercept that process. If the script you're visiting has already been compiled, the compiled bytecode is loaded instantly, either from an in-memory or on-disk cache. Most caches will also try to optimize the compiled bytecode.<br /><br />The end result is much faster PHP speeds.<br /><br />There are really only two options available nowadays:<br /><br />- The Zend Optimizer, by the company that makes PHP itself: http://www.zend.com/store/products/zend-optimizer.php<br /><br />- The Turck MMCache, which is so good that the guy behind it was hired by Zend: http://turck-mmcache.sourceforge.net/<br /><br />There were a few more players in the market, but they seem to no longer be updated and only work with really old PHPs.<br /><br />Installing and properly configuring one of these caches can result in really dramatic performance improvement...
_________________________
UBB.classic: Love it or hate it, it was mine.
|
|
Top
|
|
|
|
 |
 |
 |
 |
|
|