Yabb eat more resources ???

[Juana]

i have used yabb since version 1.3.0 and now i'm using version 1.5.1 built 48 , but lately my admin hosting told me that yabb give problem to their server.They said using up a lot of CPU resources and load average become more upper and will hangging the server.They ask me  switch to Vbuletin , i'm so pity coz i luv yabb so much,So how i can resolve this problem without switching to Vbuletin.Now my forum have been suspend by my hosting  

[Daniel D.]

Please don't double post and delete two of your posts here:
http://www.yabbse.org/community/index.php?board=9;action=display;threadid=17909;start=476

[Jeff Lewis]

I'm not sure how they could say that to you with a straight face...

1.5.1 is the best version ever of YaBB SE and is very much optimized!

[Omar Bazavilvazo]

the load here (that is a biiig site) is much lower than with any version prior to 1.5.x

ask them to be more specific. that's a lie.

[Juana]

Please don't double post and delete two of your posts here:
http://www.yabbse.org/community/index.php?board=9;action=display;threadid=17909;start=476

i have deleted , thanks .

------------------------------------------

erm i have problem with my forum db too , mysql locked the db when user written into db.here the prosess they give to me :


+------+--------------+-----------+--------------------+---------+------+---
-------------+--------------------------------------------------------------
----------------------------------------+
| Id   | User         | Host      | db                 | Command | Time
|
State          | Info
|
+------+--------------+-----------+--------------------+---------+------+---
-------------+--------------------------------------------------------------
----------------------------------------+
| 1736 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 64  
|
Locked         | SELECT
m.posterName,m.ID_MEMBER,m.posterTime,m.subject,t.ID_TOPIC,t.numReplies,
mem.realName FROM ya |
| 1747 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 70  
|
Locked         | SELECT
m.posterName,m.ID_MEMBER,m.posterTime,m.subject,t.ID_TOPIC,t.numReplies,
mem.realName FROM ya |
| 1757 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 71  
|
Locked         | UPDATE yabbse_topics SET numViews=numViews+1 WHERE
ID_TOPIC=4536                                     |
| 1758 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 70  
|
Locked         | SELECT t.ID_TOPIC FROM yabbse_topics as t,
yabbse_messages
as m WHERE (t.ID_BOARD=63 AND m.ID_MSG=t. |
| 1761 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 70  
|
Locked         | UPDATE yabbse_topics SET numViews=numViews+1 WHERE
ID_TOPIC=4663                                     |
| 1763 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 70  
|
Locked         | SELECT
t.ID_LAST_MSG,t.ID_TOPIC,t.numReplies,t.locked,m.posterName,m.ID_MEMBER,t.nu
mViews,m.posterTi |
| 1764 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 67  
|
Locked         | SELECT
t.ID_LAST_MSG,t.ID_TOPIC,t.numReplies,t.locked,m.posterName,m.ID_MEMBER,t.nu
mViews,m.posterTi |
| 1766 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 70  
|
Locked         | SELECT COUNT(*) as topiccount FROM yabbse_topics WHERE
(ID_BOARD=28)                                 |
| 1767 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 71  
|
Locked         | SELECT COUNT(*) as topiccount FROM yabbse_topics WHERE
(ID_BOARD=30)                                 |
| 1769 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 63  
|
Locked         | SELECT COUNT(*) as topiccount FROM yabbse_topics WHERE
(ID_BOARD=16)                                 |
| 1773 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 68  
|
Locked         | SELECT t.ID_TOPIC FROM yabbse_topics as
t,yabbse_topics as
top,yabbse_messages as m,yabbse_messages  |
| 1782 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 61  
|
Locked         | SELECT COUNT(*) as topiccount FROM yabbse_topics WHERE
(ID_BOARD=4)                                  |
| 1786 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 58  
|
Locked         | SELECT COUNT(*) as totalm FROM yabbse_messages as
m,yabbse_boards as b,yabbse_topics as t,yabbse_cat |
| 1788 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 52  
|
Locked         | SELECT COUNT(*) as topiccount FROM yabbse_topics WHERE
(ID_BOARD=74)                                 |
| 1791 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 47  
|
Locked         | SELECT t.ID_TOPIC FROM yabbse_topics as
t,yabbse_topics as
top,yabbse_messages as m,yabbse_messages  |
| 1795 | tokeiked     | localhost | tokeiked_kedaikopi | Query   | 32  
|
Locked         | SELECT COUNT(*) as totalm FROM yabbse_messages as
m,yabbse_boards as b,yabbse_topics as t,yabbse_cat |
+------+--------------+-----------+--------------------+---------+------+---
-------------+--------------------------------------------------------------
----------------------------------------+
92 rows in set (2.55 sec)

[Derek]

I got a phone call from my host as well. It turns out that the clicklog was causing all the problems. It was keeping 80+ connections alive at a time, and seriously crapping things up. Anyways, simple solution, I patched the code, removing any mention of the clicklog from the code, and had the problem fixed before I was even off hold. It was a bugger coding with the telephone on my shoulder.

[[Unknown]]

*whistles*

Good thing I removed the click log from my project, isn't it?

*whistles*

-[Unknown]

[Juana]

i'm not a coder derek . .so i did't know how to do like yours. can you tell me how to do that or anyone can give me solution ....plzzzzz

[David]

Sorry to say this but your host is full of sh*t.  If 80 connections are being kept open it is because of MySQL being configured wrong, has nothing to do with YaBBSE.

[Juana]

erm ........  

[Spaceman-Spiff]

if u're running zlib compression/Enable Compressed Output, u can disable it too

[Jeff Lewis]

Easy way to stop the ever annoying click log is to comment out the call to it right in index.php.

The function call is Click_Log() I believe, just add a comment marker in front of that //

[acf [delete me]!]

*whistles*

Good thing I removed the click log from my project, isn't it?

*whistles*

-[Unknown]

Hmmm intresting  

[groundup]

yea, your host is dumb. It must be caused by 1 of 2 things.. 1 - mysql not being config'd right.. 2 - another program.

PS: how about a mod to remove the clicklog?

[[Unknown]]

Code Select Expand

<edit file>
index.php
</edit file>

<search for>
/* ### Log this click ### */
ClickLog();
</search for>

<replace>
/* ### Do not log this click ### */
//ClickLog();
</replace>

Wow that was hard .

-[Unknown]