Thanks guys.
braeden said:
I don't know why you guys didn't just copy the forum directory & SQL database to a separate folder, set up the new forums and then merge that folder into the root directory on the server when the new install was finished. That way there would have been less downtime and we'd still be able to access the forums.
:'(
Braeden, the issue wasn't that simple.
Initially I thought I'd have it done in a day.
It took 2 days to convert the entire GroupDIY database--twice it stalled so I had to restart from scratch. And that was with just 10ms delay intervals between each SQL query on an Intel i5 2.8GHz dual core processor with 16G RAM and SSD.
The db structure was being converted from SMF to BBpress. I had to lock the old db before doing the conversion to ensure the converted db would be in sync with when the conversion finished.
After 2 failed conversions, the 3rd went well. Running some tests everything looked good.
Then...
1) I opened the site back up...instant flood of traffic. Server crash.
2) OK... No problem. Reboot, and throttle traffic until the cache builds back up.
3) Allotted 512MB for the opcode cache (that's a big cache for 1 site, for instance we're running great now with 128MB) got primed, opened the gate again... OK for 15mins, crash.
4) Fine, lets try 1G...nope. How about 2G...nope. Let's just be stupid and try 4G. That was good for an hour but still, nope.
5) The 10th day 11th hour decision was to revert back to SMF.
There's a big performance/scalability issue with BBpress if a moderately large site like GroupDIY can't run without maxing out our box on modest traffic--even when allowing a stupid amount of memory for the cache to offload redundant CPU cycles. After having invested so much time into the conversion, I could have tried throwing more hardware at it as a brute force solution...but, that just seemed silly.