By Tom-E on

My site is very busy, and full of nodes. Since its a Vbulletin setup, a lot of people browsing the site are "authenticated" and not just "anonymous"

I beleive in Drupal 4.6 "authenticated users" were cached just like anonymous... Is there anyway to get this in 4.7?

I feel very lucky if my server stays up for more then 2 days at a time... I sincerely need to fix this problem.

--------------------
Ive been trying to setup "fastpath_fscache" but after installing the module step #4 says that a link in my Admin menu will showup, yet nothing is there, so I cant do anything.

Static caching would really help.

-- The requirement for this module is "Drupal HEAD" what is this?! No explanations come from a Google Search, just the HEAD API.

What can I do to help my site stay up more?

Thanks for any replies :-)

Tommy

⋅ Categories: Drupal 4.7.x

Comments

bdragon’s picture

bdragon commented

I'll answer your last question first:

"Drupal HEAD" refers to the bleeding-edge development version of Drupal in CVS. What this means exactly changes every so often. Currently, HEAD is the code branch that Drupal 5.0 will come from. When Drupal 5.0 is released, it will branch off from HEAD, and HEAD will then be the code leading up to whatever the next Drupal will be in the future. (Drupal 5.1? 6.0? Nobody knows.)

This all happens in parallel. Drupal 4.6, 4.7, and (not even in beta yet) 5.0 all have different branches in the CVS tree.

http://en.wikipedia.org/wiki/Branching_(software)

Since the fastpath_fscache is developed against HEAD, it will NOT work with ANY 4.7.x release without modification, including a 4.7.x release that happens after 5.0 is released.

About your problems with caching:
I don't think caching for authenticated users is the proper solution to your problem. Drupal.org gets along ok without authenticated user caching. There are currently 134 people logged in. Is your site busier than that? How busy are we talking, exactly?

There is most likely something causing a bottleneck somewhere. One poorly-behaving module can wreck the performance for an entire site. Install devel.module and see if you can find any database queries that are taking an unusually long time to run.

Tom-E’s picture

Tom-E commented

Thanks for the help, but I dont understand why the fastpath_fscache module (http://drupal.org/project/fastpath_fscache) requires HEAD...

This means that you cant use it in 4.7? There was another posting of some code modifications that could be made about half a year before that module was posted, supposed to do the same thing, so ill have to check that out i guess.

For now i installed Block Cache (caches blocks, doesnt block the cache ;-) /) and i upped my minimum cache time.

My site typically has about 400 people on at a time, usually half are authenticated users...

I also have a few hundred nodes on my site...

bdragon’s picture

bdragon commented

It requires HEAD because the APIs it uses are different in 4.7 and HEAD. It might be possible to backport it.

That's a high people to node ratio you got there...

What kinds of nodes? Are you having heavy spider traffic? Does your webserver's error log grow suddenly when someone edits a node?