[sadegazoz]

dude just try this answer from argh2xxx for my question:

"You have phpmyadmin? Or do you know how to access your mysql database? If you have phpmyadmin, go to the correct database of your pligg, and then go to the tab say mysql, and then enter the command of:

alter table pligg_links add index(link_status);

After you done that, you gotta wait for few minutes depend on how large is your database, and then when it's done, your website speed up a bit.

If you take a look at your database now, and in the table of pligg_links you will see a column said link_status."

[rubber2002]

Originally Posted by sadegazoz

dude just try this answer from argh2xxx for my question:

"You have phpmyadmin? Or do you know how to access your mysql database? If you have phpmyadmin, go to the correct database of your pligg, and then go to the tab say mysql, and then enter the command of:

alter table pligg_links add index(link_status);

After you done that, you gotta wait for few minutes depend on how large is your database, and then when it's done, your website speed up a bit.

If you take a look at your database now, and in the table of pligg_links you will see a column said link_status."

Thanks Sadegazoz

[argh2xxx]

Is there any other way to speed up pligg? As I got 100,000 of links... And adding index is not helping much...

[deals311]

I have used MySQL with 10's of thousands of records without indexes and it rocks. I wouldn't rush into this until someone proves it is necessary. Adding indexes is just adding another SPOF (single point of failure). If it's proven beneficial then by all means lets do it.

Something I have found is that returning 10 rows or 500 rows on a dynamic web page takes about the same amount of time. (not tested in pligg enviornment). The overhead in the communications is by far the bottle neck. User communicating to web -> web to mysql -> back again.

[RTM]

I agree - I for one have deployed about 10-20 Pligg based sites for various clients on everything from shared hosting right up to dedicated on a single socket quad-core Dell 2950 box with 4GB of ram (the latter one had serious of traffic as in 50-100 uniques per minute)....

but in all cases over the last 2 years, I have found Pligg to be seriously resource intensive. Throwing hardware resources (CPU, RAM, bandwidth, etc) does not seem to be a universal situation so me thinks thet SQL optimisation is a serious viable approach!

Still waiting for more tangible proof that these indexes help performance, but I'm looking forward to it!

Rob

[knockoutchris]

Changed my load time from 9s to 4.5s

[joehunk]

Is there any other solution to speed up pligg aside adding indexes? I implemented this on my site and have the same speed (no improvement). I believe SQL optimization is the best solution. Looking forward to this. I think it is the main priority, removing stories on my site is not my Option

[winbooz3]

[repute]

Ow no I cant publisch links in admin_links.php anymore after I had done this!
Also after dropping the index i can't publish stories in the admin.

Also my stats in de admin aren't woring aanymore it says 0 stories :S

And i also getting the following error:

Warning: Unknown column 'published' in 'where clause' in /home/domains/domain.com/public_html/libs/db.php on line 233

Warning: Unknown column 'queued' in 'where clause' in /home/domains/domain.com/public_html/libs/db.php on line 233

Warning: Unknown column 'links' in 'where clause' in /home/domains/domain.com/public_html/libs/db.php on line 233

Please help me!

[repute]

BUMP please help me!