Hello.
Reading the opened post with regard to the problems of speed pligg I have concluded that is very probably that the real problem are the sql queries.
I am aware that sites like tecnhorati or wikio should have multiple servers to work with even dedicated servers for mysql.
But I can not believe that a site with 40/50.000 stories and 500 unique visitors per day has the need to erase the oldest stories, comments and other parties to avoid the collapse of the server or should take a dedicated server all'sql.
Today my Xenfra.com has 57,000 stories and 21,000 pages indexed on google. its strength for the future is precisely the number of pages that Google indexes and that may be clicked by users.
But the server (quad-core with 2 gb ram) is having problems and few solution configuration php and sql are the only suggest that I have found. The only real solution is to delete the old stories and take another server.
Thinking in this manner pligg will always be a platform that does not guarantee the ability to monetize gain because the relationship between resources necessary hardware and traffic is not commensurate with the revenue.
I unfortunately can not make the necessary changes ... I’m not so good.
But I can also contribute significantly so that this problem be addressed once and by developers pligg.
I am sure that a poll would emerge many other users of pligg available to fund these changes as long as these changes become a priority compared to many other things which are not there do nothing if pligg turns evil.
Good work at all.






Linear Mode




