The Real Cause Of High Load For My Server Using PLigg 9.9 and Was 9.8.2

[argh2xxx]

I found the cause of the high load is from mysql by user 'mypligg'


PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2788 mysql 21 6 180m 107m 3660 S 396 3.5 1315:58 mysqld


[root@server ~]# mysqladmin proc
+-------+-----------------+-----------+-----------------+---------+------+----------------------+------------------------------------------------------------------------------------------------------+
| Id | User | Host | db | Command | Time | State | Info |
+-------+-----------------+-----------+-----------------+---------+------+----------------------+------------------------------------------------------------------------------------------------------+
| 29083 | mypligg | localhost | mypligg | Query | 10 | Locked | SELECT count(*) FROM pligg_links WHERE link_url = 'http://www.msnbc.msn.com/id/7969739/displaymode/1 |
| 37912 | mypligg | localhost | mypligg | Query | 21 | Locked | UPDATE pligg_links set `link_reports`=0, `link_comments`=0, link_author=1, link_status='published', |
| 46126 | mypligg | localhost | mypligg | Query | 21 | Locked | UPDATE pligg_links set `link_reports`=0, `link_comments`=0, link_author=1, link_status='published', |
| 47538 | mypligg | localhost | mypligg | Query | 21 | Locked | UPDATE pligg_links set `link_reports`=0, `link_comments`=0, link_author=1, link_status='published', |
| 48385 | mypligg | localhost | mypligg | Query | 32 | Sorting result | SELECT link_id FROM pligg_links WHERE link_status='published' ORDER BY link_date DESC LIMIT 0,5 |
| 48395 | mypligg | localhost | mypligg | Query | 3 | Locked | SELECT pligg_links.* FROM pligg_links WHERE link_id = 131424 OR link_id = 131423 OR link_id = 1 |
| 48397 | mypligg | localhost | mypligg | Query | 21 | Locked | UPDATE pligg_links set `link_reports`=0, `link_comments`=0, link_author=1, link_status='published', |
| 48409 | mypligg | localhost | mypligg | Query | 20 | Locked | SELECT link_id FROM pligg_links WHERE link_status!='discard' AND (link_category=6 ) ORDER BY link |
| 48410 | mypligg | localhost | mypligg | Query | 32 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48412 | mypligg | localhost | mypligg | Query | 20 | Locked | SELECT pligg_links.* FROM pligg_links WHERE link_id = 131233 OR link_id = 130948 OR link_id = 1 |
| 48415 | mypligg | localhost | mypligg | Query | 8 | Locked | SELECT pligg_links.* FROM pligg_links WHERE link_id = 131424 OR link_id = 131423 OR link_id = 1 |
| 48416 | mypligg | localhost | mypligg | Query | 31 | Sorting result | SELECT link_id FROM pligg_links WHERE link_status='published' ORDER BY link_date DESC LIMIT 0,5 |
| 48417 | mypligg | localhost | mypligg | Query | 5 | Locked | SELECT pligg_links.* FROM pligg_links WHERE link_id = 131424 OR link_id = 131423 OR link_id = 1 |
| 48508 | mypligg | localhost | mypligg | Query | 31 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48509 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48511 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48510 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48512 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48513 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48514 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48515 | mypligg | localhost | mypligg | Query | 29 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
And a lot more of these bu I only posted a few.|
+-------+-----------------+-----------+-----------------+---------+------+----------------------+------------------------------------------------------------------------------------------------------+

The similar querries to the above made my server's load shot up to 30 and sometime 38, and can go even more beyond than just those two digit numbers. This is a dedicated dual core dual processor Xeon with 3GB and SCSI HD.

[ablaye]

And your point is?

[argh2xxx]

To be serious on PLIGG is like to build a real Digg. Resources intensive and need cluster of dedicated database servers. At now pligg on my site is slow to a crawl. Worst than 56k modem. Yes I'm using dedicated server too. For production, Pligg is intensive, but for fun, anyone can do so.

I just hope Pligg creator can come up with a version where really lean and clean querries to the database somehow, and cut down the use of intensive resources by half.

My point is that I'm trying to tell what I know, and hope the creator take this to mind and come up with a better product. Not attacking, but trying to point out what's there. If my point is not important to you, then I guess this thread is meaningless to you, but it's important to me as you can see I'm a serious Pligg user, and so I hope for a better Pligg version where database querries will not be a factor.

Pligg is open source and so I don't dare to say much, but I don't mind buying Pligg if Pligg creator comes out with a commercial one where no intensive resource querries to the database, and less buggy version. I have always buy softwares and use whatever open sources that are available. It's a balance thing that I got going, but the point I want to make is that Pligg is not yet ready for the real real intensive production environment. My website is not even busy as others, I mean you can look on Alexa and see my website traffic, it's not even close to busy, and yet Pligg is crawling.

[Redux]

Dude your on a shared host -_-

[sanchopanza]

Originally Posted by argh2xxx

To be serious on PLIGG is like to build a real Digg. Resources intensive and need cluster of dedicated database servers. At now pligg on my site is slow to a crawl. Worst than 56k modem. Yes I'm using dedicated server too. For production, Pligg is intensive, but for fun, anyone can do so.

I just hope Pligg creator can come up with a version where really lean and clean querries to the database somehow, and cut down the use of intensive resources by half.

My point is that I'm trying to tell what I know, and hope the creator take this to mind and come up with a better product. Not attacking, but trying to point out what's there. If my point is not important to you, then I guess this thread is meaningless to you, but it's important to me as you can see I'm a serious Pligg user, and so I hope for a better Pligg version where database querries will not be a factor.

Pligg is open source and so I don't dare to say much, but I don't mind buying Pligg if Pligg creator comes out with a commercial one where no intensive resource querries to the database, and less buggy version. I have always buy softwares and use whatever open sources that are available. It's a balance thing that I got going, but the point I want to make is that Pligg is not yet ready for the real real intensive production environment. My website is not even busy as others, I mean you can look on Alexa and see my website traffic, it's not even close to busy, and yet Pligg is crawling.

Now I don't know what tool Chuckroast used to analyze my site, but he pointed out some very good suggestions for me to improve performance.

Compress js and disable some modules, if you take a look see you'll find them in the forums

you may benefit similarly as i have seen a marked improvement in my site performance

[AshDigg]

Originally Posted by argh2xxx

I found the cause of the high load is from mysql by user 'mypligg'


PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2788 mysql 21 6 180m 107m 3660 S 396 3.5 1315:58 mysqld


[root@server ~]# mysqladmin proc
+-------+-----------------+-----------+-----------------+---------+------+----------------------+------------------------------------------------------------------------------------------------------+
| Id | User | Host | db | Command | Time | State | Info |
+-------+-----------------+-----------+-----------------+---------+------+----------------------+------------------------------------------------------------------------------------------------------+
| 29083 | mypligg | localhost | mypligg | Query | 10 | Locked | SELECT count(*) FROM pligg_links WHERE link_url = 'http://www.msnbc.msn.com/id/7969739/displaymode/1 |
| 37912 | mypligg | localhost | mypligg | Query | 21 | Locked | UPDATE pligg_links set `link_reports`=0, `link_comments`=0, link_author=1, link_status='published', |
| 46126 | mypligg | localhost | mypligg | Query | 21 | Locked | UPDATE pligg_links set `link_reports`=0, `link_comments`=0, link_author=1, link_status='published', |
| 47538 | mypligg | localhost | mypligg | Query | 21 | Locked | UPDATE pligg_links set `link_reports`=0, `link_comments`=0, link_author=1, link_status='published', |
| 48385 | mypligg | localhost | mypligg | Query | 32 | Sorting result | SELECT link_id FROM pligg_links WHERE link_status='published' ORDER BY link_date DESC LIMIT 0,5 |
| 48395 | mypligg | localhost | mypligg | Query | 3 | Locked | SELECT pligg_links.* FROM pligg_links WHERE link_id = 131424 OR link_id = 131423 OR link_id = 1 |
| 48397 | mypligg | localhost | mypligg | Query | 21 | Locked | UPDATE pligg_links set `link_reports`=0, `link_comments`=0, link_author=1, link_status='published', |
| 48409 | mypligg | localhost | mypligg | Query | 20 | Locked | SELECT link_id FROM pligg_links WHERE link_status!='discard' AND (link_category=6 ) ORDER BY link |
| 48410 | mypligg | localhost | mypligg | Query | 32 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48412 | mypligg | localhost | mypligg | Query | 20 | Locked | SELECT pligg_links.* FROM pligg_links WHERE link_id = 131233 OR link_id = 130948 OR link_id = 1 |
| 48415 | mypligg | localhost | mypligg | Query | 8 | Locked | SELECT pligg_links.* FROM pligg_links WHERE link_id = 131424 OR link_id = 131423 OR link_id = 1 |
| 48416 | mypligg | localhost | mypligg | Query | 31 | Sorting result | SELECT link_id FROM pligg_links WHERE link_status='published' ORDER BY link_date DESC LIMIT 0,5 |
| 48417 | mypligg | localhost | mypligg | Query | 5 | Locked | SELECT pligg_links.* FROM pligg_links WHERE link_id = 131424 OR link_id = 131423 OR link_id = 1 |
| 48508 | mypligg | localhost | mypligg | Query | 31 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48509 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48511 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48510 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48512 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48513 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48514 | mypligg | localhost | mypligg | Query | 30 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
| 48515 | mypligg | localhost | mypligg | Query | 29 | Copying to tmp table | select *, count(*) as count from pligg_links, pligg_categories where category_lang='en' and categor |
And a lot more of these bu I only posted a few.|
+-------+-----------------+-----------+-----------------+---------+------+----------------------+------------------------------------------------------------------------------------------------------+

The similar querries to the above made my server's load shot up to 30 and sometime 38, and can go even more beyond than just those two digit numbers. This is a dedicated dual core dual processor Xeon with 3GB and SCSI HD.

Those update ones are interesting, I'll look into that. The last couple ones, the category type ones, I'm working on those ones and should be fixed for the next release.

thanks

[argh2xxx]

I just open an account with media temple and upload solely pligg database onto media temple. The same result appeared. What I mean by this is that when you go to blogmyway.org/papadodo now, you'll see it's impossible to load thing fast and even for voting, when click on vote, it take at least 30 sec for the vote to update.

Media temple is using grid, and I guess their grid is the same as my server. LOLz... or may be the grid is not as good as a dedicated server, as you can see sharing is bad

Unless they capped how much resources a user can get... etc...

Though I prefer this way on media temple unless they complained, then I have to move the databse, otherwise, it stays on media temple for now. LOLz... I don't want pligg to querry my the database on my server, because it will slow other part of my server down badly too.

Don't flame me because of this, I pay $20 and I'm using the account

[bbrian017]

I think pligg is pretty fast but maybe it's the lack of content I have on my pligg site.. I only have 400 members and 700 articles

I also have shared hosting but still think the software is pretty fast personally!

[argh2xxx]

I have over 140,000 articles, maybe that is why it is slow?

[dollars5]

Originally Posted by argh2xxx

I just open an account with media temple and upload solely pligg database onto media temple. The same result appeared. What I mean by this is that when you go to blogmyway.org/papadodo now, you'll see it's impossible to load thing fast and even for voting, when click on vote, it take at least 30 sec for the vote to update.

Media temple is using grid, and I guess their grid is the same as my server. LOLz... or may be the grid is not as good as a dedicated server, as you can see sharing is bad

Unless they capped how much resources a user can get... etc...

Though I prefer this way on media temple unless they complained, then I have to move the databse, otherwise, it stays on media temple for now. LOLz... I don't want pligg to querry my the database on my server, because it will slow other part of my server down badly too.

Don't flame me because of this, I pay $20 and I'm using the account

I would have to disagree on the MediaTemple part - I own two DV servers there and each running of about 40+ pligg sites (majority demo and few production) an average of 20,000 unique visits per day of each servers and extremely no problems at all. Mind you that server is not a Dual Core Xeon, and only 256 MB RAM. I have mod_gzip enabled for all and sites load great.

But I have had problems with all other hosts when using Pligg on the slowness part - I know the database calls are not that optimal and any help/suggestions in optimizing it are always welcome.

BTW: On the grid that you mentioned with MT - did they give you a root access to run pid?