11
karuna
Re: Xoops overloading my Server
  • 2005/4/20 19:27

  • karuna

  • Not too shy to talk

  • Posts: 171

  • Since: 2002/5/29


maybe u have also to cache newbb for 30 second.

newbb use a lot of query.

u can turn on mysql/block debug to see how many queries a page cost. cache these page which have too many queries.

however i think the XOOPS should cache some config or store some config in file (like XOOPS 1.x).

use phppp's update cache on change hack will have some help.

there's another hack will reduce query.

cache XOOPS and module config. but it's in Chinese

https://xoops.org.cn/modules/newbb/viewtopic.php?topic_id=2072&viewmode=flat&order=DESC&start=20 (config cache)

http://my.ppfans.com/module.php.txt (module config cache)

12
Skythe
Re: Xoops overloading my Server
  • 2005/4/21 16:37

  • Skythe

  • Just popping in

  • Posts: 99

  • Since: 2004/7/2 2


Thanks guys. Im gonna sit tight and wait till my hosts tells me what the situation is now before making any more changes. And loading speed of the pages is better than ever now anyway.

But looks like the caching has created a new problem.

Forum cache is set to 1 hour. Ive just posted 4 times in different threads and while I could see the first 3 posts after posting them, when I posted the 4th, it wouldnt appear at the bottom of the page. I reloaded the page, went back to the other threads, and all 4 posts are gone.

13
Herko
Re: Xoops overloading my Server
  • 2005/4/21 16:45

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


yeah, that is what caching is all about: it generates a static page that is loaded for an hour, in stead of building the page dynamically every time that page is loaded. That is why the caching reduces the number of queries so significantly. Set the cache on your forum to as low as possible a time interval (or even 0) and see if that is still acceptable.

Hekro

14
karuna
Re: Xoops overloading my Server
  • 2005/4/22 7:17

  • karuna

  • Not too shy to talk

  • Posts: 171

  • Since: 2002/5/29


Quote:

Skythe wrote:
Thanks guys. Im gonna sit tight and wait till my hosts tells me what the situation is now before making any more changes. And loading speed of the pages is better than ever now anyway.

But looks like the caching has created a new problem.

Forum cache is set to 1 hour. Ive just posted 4 times in different threads and while I could see the first 3 posts after posting them, when I posted the 4th, it wouldnt appear at the bottom of the page. I reloaded the page, went back to the other threads, and all 4 posts are gone.

use phppp's update cache on change hack

15
Skythe
Re: Xoops overloading my Server
  • 2005/4/27 15:10

  • Skythe

  • Just popping in

  • Posts: 99

  • Since: 2004/7/2 2


The number of querries is higher than ever now. First ~380, then down to around 30 when I reduced the # of news entries, now ~620 on the front page. Without my having changed a thing.

Whats this all about?


EDIT: 770 today

16
Skythe
Re: Xoops overloading my Server
  • 2005/4/30 10:31

  • Skythe

  • Just popping in

  • Posts: 99

  • Since: 2004/7/2 2


5.363 Seconds | 1015 Queries :x

17
Mithrandir
Re: Xoops overloading my Server

Can you give a link to the site, so we can perhaps see what is going on?

18
Skythe
Re: Xoops overloading my Server
  • 2005/4/30 13:12

  • Skythe

  • Just popping in

  • Posts: 99

  • Since: 2004/7/2 2



19
LazyBadger
Re: Xoops overloading my Server

Just to note (unrealated to overload thing) - I went on site and have admin's rights on News module (see links "Edit" and "Delete" on front page)

20
Mithrandir
Re: Xoops overloading my Server

Sorry - missed that one.

I get
Quote:
Page generated in 0.354 Seconds | 32 Queries

as anonymous. Where do you reach 1000+ queries? Is it only when logged in?

Login

Who's Online

158 user(s) are online (104 user(s) are browsing Support Forums)


Members: 0


Guests: 158


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits