look per, i for one build systems designed to scale to popular levels. that means that whatever i can squeeze out of a single machine will save me money. quite a lot, coz as you know dedicated hosting gets very expensive when you have to buy fast machines. threading features and persistent shared memory _would_ decrease cost, a lot, for any php app that wants to scale to popular levels. i'd like to keep coding in php, and not have to switch languages because my app got popular. On Wed, Mar 24, 2010 at 9:46 AM, Per Jessen <per@xxxxxxxxxxxx> wrote: > Robert Cummings wrote: > >> Yes, I do. There's nothing in your requirements above that sound >> particularly difficult for PHP to handle with a good design and lots >> of caching... and of course the right hardware. I think you're hung up >> on the numbers a bit... those aren't very big numbers for a database. > > Yeah. Given a decent database machine, those 5 millions rows can be > kept in-core all the time. > > > > -- > Per Jessen, Zürich (7.8°C) > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
