[eluser]WanWizard[/eluser]
I wasn't talking about performance, but memory usage. I know you can't make any statements about performance if you don't use a controlled environment.
Tests have been conducted with identical code and database. Apache and MySQL have been restarted prior to the tests. On a side note: even if we don't do that, but we repeat the tests after a days of hard work, the figures are the same as with the first test of the day. There is hardly any variation (just bytes) in the memory usage a given machine reports, no matter when you run the tests, and what you have done prior to testing.
The machine with the lowest specs always reports the lowest memory consumption.
I can't really accept that this happens just because the difference in specs. That would mean that PHP's memory allocation algorithm is seriously flawed, why would it report a 2 meg difference in memory consumption when processing exactly the same code, running the same queries, producing the same results?
The specs call for a PHP memory limit of max. 32M, so there is no immediate issue. I'm going to try to find a machine with similar specs as the production server is going to have, and see what happens there. I'm not to worried at the moment, but when I see something I can't explain, I start looking for an explaination. ;-)
As to your BTW: our developers roam, the repository doesn't. Even if they're on the road or at home, they're always online (thanks to flat-fee 3G or broadband), so no issues there. We might switch to git eventually (but that's a business decision which means repo conversions, different toolsets, etc), but currently I don't see the benefits...
