Ditchmonkey Posted June 15, 2009 Posted June 15, 2009 [quote name='bfarber' date='15 June 2009 - 10:34 AM' timestamp='1245090869' post='1810340'] We pretty much always put our early pre-final releases on these forums in order to test, profile and discover issues that you just can't nail down in a development environment. I mean, I don't have half a million posts and 500 users online on my localhost - it's sometimes not possible to see that there is an issue with a feature until you put it in a live environment. I'm not saying its a bad idea to have public beta tests. However to have a public beta test on a server that you know would likely cause performance issues is not a good idea and that was what I was referring to. Gotta put your best foot forward at all times and sharing resources in this case had some negative effects that could have turned off future customers. And yes, its fine now :) BTW I bought the suite today to start initial testing for future projects. Probably wouldn't have happened if there were still doubts about performance.
Management Charles Posted June 15, 2009 Management Posted June 15, 2009 I get where you're coming from, Ditchmonkey :) ... Brandon was just saying that a benefit to having public testing on a slow server is that any performance issues in IPB3 showed up REALLY quickly and we could diagnose them. Sort of a fringe benefit.
dieselpowered Posted June 16, 2009 Author Posted June 16, 2009 I agree, you would likely want to test on a server config that the average user would have versus someone who has the benefit of a dedicated server.
sparc Posted June 16, 2009 Posted June 16, 2009 It's blazing fast right now. Did you guys tweak it even further after the server change?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.