I have enabled Drupal normal cache. Improves a lot. Unfortunately only for anonymous users.

What about memcache? Would this bring another performance improvement? I read article that says enabling memcache wont bring significant performance boost.

http://2bits.com/articles/advcache-and-memcached-benchmarks-with-drupal....

Regards

Comments

I haven't tried memcache

I haven't tried memcache yet, but have tried Advanced Cache - to use it you have to run the patch files on Drupal core. For me it caused significant performance gains for logged in users (I primarily tried out the forum and path caches... both of which are evidently broken now in the current version for some reason - I believe I tried it on Drupal 5.7 using the 1.6 version - maybe it's broken for 5.9 or the broken notes refer only to the dev version... I haven't tried the other patches carefully yet).

If I'm understanding the article/benchmarks you referred to, it looks like it is comparing Drupal's core caching versus memcache for anonymous users. Robert Douglass suggests the combination of both Advanced Cache and memcache for improving things for logged in users.

-- David
absolutecross.com

hmm..

Now I confused...

1. Should I use Drupal cache with memcache?
or
2. Should I use Drupal cache with file based cache?

Which offers better performance?
Regarding advanced cache yes I have implemented it recently and quite a performance gain.

Regards

About Caching

Hope this will give u clear idea about caching

1. Content Caching
cache_set($cid, $data, $table = 'cache', $expire = CACHE_PERMANENT, $headers = NULL);

cache_get($cid, $table = 'cache')
cache_set now automatically serializes arrays and objects passed to it before saving them to the cache table. When retrieving data from the cache, cache_get now automatically unserializes the data when necessary. Simple datatypes such as strings and integers do not need to and will not be serialized before being stored

2. Block Caching
$blocks[0]['cache'] = BLOCK_CACHE_PER_PAGE | BLOCK_CACHE_PER_ROLE(default);
Drupal 6 now has a block-level cache, which improves performance for both authenticated and anonymous users. Site administrators can turn on block caching on the 'Performance' settings page(admin/settings/performance).

3. Menu Caching
menu_cache_clear($menu_name = 'navigation')

cache_clear_all($cid = NULL, $table = NULL, $wildcard = FALSE)
By default each menu item clicked is cached. For clearing particular menu item clicked we can use
cache_clear_all.
menu_cache_clear clears all menu cached.

4. Form Caching
form_set_cache($form_build_id, $form, $form_state)

form_get_cache($form_build_id, &$form_state)
In Drupal 6 the whole form can be stored in database using form cache. $form_build is our unique name for form to be cached.
$form is an array where it contains all form structure like textfield, checkboxes etc.
$form_state is an array which contains submitted or storaged.

5. Page Caching
Recommended Page Caching is Normal. Minimum cache life time can be set to clear page caching.
Site administrators can turn on page caching to “Normal” on the 'Performance' settings page(admin/settings/performance). For anonymous users page gets cached as blob/image in cache_page table.

6. Memory Caching (Memcache)
$memcache->set($key,$object,MEMCACHE_COMPRESSED,$timeout)

$memcache->get($key)
memcache used to speed up dynamic database-driven websites by caching data and objects in memory to reduce the number of times the database must be read. So instead of requesting lot of queries when a page is load, memcache stores result set of queries in server. And it fetches results from that instead of running queries. It his highly used for linux servers

6. Mysql Query Caching
set global query_cache_size=50000000;

Mysql query cache stores the SELECT queries issued by clients to the MySQL database server. In this respect, it acts a lot like traditional database SQL caches, in that identically issued queries will be located and re-issued by the database engine without hard parse activity. However, unlike any other database system, MySQL stores not only the SQL query issued by a client, but also stores the query's result set

7. Turck MMCache

Only Installation is required.
Turck MMCache is a opcode cache for PHP. It increases performance of PHP scripts by caching them in a compiled state, so that the overhead of compiling is almost completely eliminated. It also uses some optimizations for speeding up PHP scripts' execution. It typically reduces server load and increases the speed of PHP code by 1-10 times.
Other Caching Methods : APC , XCACHE, eAccelerator (Not Recommended to use for drupal)

But for better performance on Drupal: Turck MMCache is used rather than APC , XCACHE, eAccelerator. Similarly modules for those three were not developed on drupal. fastpath_fscache is for file caching, but there is no module developed for drupal 6.

Thanks
Devaraj
Analyst Programmer
Netlink Technologies.

Deva

oh no...

Sorry reading your info makes me more confused. Cause I am not a technical person..

I am using 5.7. What components that Drupal default cache is doing?
Why fastpath_fscache is not developed for drupal 6?

So according to your opinion what should I use?
Drupal cache with memcache? Or Drupal cache with file based caching?

Regards.

So which one better? Drupal

So which one better??

Drupal cache with memcache or Drupal cache with file based caching like fastpath_fscache

Regards

So which one better? Drupal

Here i posted one forum on drupal kindly check with that link .. if that too does not make sense .. then get back ..

http://drupal.org/node/288488

Thanks
Devaraj.

Deva

Very sorry I dont understand

Very sorry I dont understand this technical stuffs. I only need your opinion which gives me better performance?
Currently I have enabled Drupal Cache to normal via admin-settings-performance and I also have enabled CSS and JS aggregation.

Now I am considering file based caching like fastpath_fscache and boost. Or? a memcache?

Regards n Thanks

Well, it all depends on what

Well, it all depends on what site you're building.
I'll try to explain in a less technical way.

Caching for anonymous user

  • Normal DB Caching
    This should be enough for common folks
  • Aggresive DB Caching
    This one may have side effects, though it provides considerable performance boost than normal caching
  • FastPath FSCache
    This one is using files to store cache as opposed to both the above approach, thus bypassing database connection.
  • Boost
    This beast uses files for caching as well. It uses really cool mod_rewrite trick, thus bypassing php and database.
    Absolutely the winner here :D. Nearly the same speed as serving static html pages.
    Though it's worth noted that this one is the trickiest to install. Expect problems with this one.
    If you do happen to use it without any notable issues. Please let us know :)

That's it for now. I'll let the others fill in the rest.

PS: If you're ready for more advanced stuff, check out "cache router" as well.

EtradingGallery

-=- Jhon -=-

EtradingGallery

-=- Jhon -=-

Using Boost with Lighttpd

Using boost with lighttpd.

1) Using cron to refresh expires pages (that expire every 10 mins) every 15 mins.
2) Put in a hack to not expire 'node' type pages since boost effectively wipes out node type cached files when they are updated. If they are not updated, no need to recreate cache files.
3) Frequently visited pages which has dynamic content that get's aggregated on a page , like an aggregated page made up of panels with views output in one of the panes, are getting refreshed every 15 mins by use of option (1).
4) Had to write the lighttpd / lua rules to work boost with lighty.

Very pleased with the results so far.

So what scenerio is best for performance?

I use ZendOptimizer and ZendFramework on mysite.

is ZendOptimizer a type of optcode cache like MMCache or eAccelerator?

So it sounds like one would use memcache OR fast_cache OR boost OR database query cache because they each save and retreive information from different places. Is that the case?

Is this right?
Advanced Cache. Advanced Cache is for logged in users.
Boost is for anonymous users
Drupal performance tab only affects anonymous users. is that correct?

So I could use an optcode performance enhancer for PHP like eAccelerator in conjunction with a caching booster above.
Selecting memory based over database based over file based caching is really upto whatever my resources are.

Is it also safe to say that memory cache will give you better performance over file based cache over database cache?

is that correct.

Thanks for your help

Chris

http://SocialNicheGuru.com
Creating gurus to deliver the right product and the right message to the right niche at the right time

any other cache for

any other cache for authenticated users?

only advanced cache available?

before that. thanks for all the info here.

Regards

nobody click here