I doubt it's the software itself (I run Tiki too... It's just PHP.) It's purely a matter of scaling. What part is causing the load? The PHP apache processes? The DB server? Both? What performance tuning has been done? Is it a custom apache compiled for this app or is it a generic distro version with all the extra modules? What about the disk? Is it fast enough (slow disk can cause high load average numbers as you spend all your time in I/O Wait.) Is there enough RAM? What else is the machine used for?
Whatever is causing load problems can be analyzed and solved. May need hardware thrown at it. May not. In any case, scaling tiki up is easy - all it takes is time and money. You can throw multiple front-end and back-end servers at it to handle any reasonable load (we are not talking Yahoo levels here...) Converting the content (as is the case with many Wiki's) to another wiki system can be quite painful. Each uses their own wiki notation and has their own list of features. Converting is usually a last resort. On Wed, Jun 22, 2005 at 01:29:35PM -0500, Jay Milk said: > As I understand it, the wiki software behind voip-info is not able to > keep up with the load. There may be better (-performing) alternatives > such as MediaWiki, but the question would be that of conversion... And > whether the owner even wants to convert. _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
