Cache search results [#242187]

hi,

i want to improve my search module. when user search a record based on keyword, the records will retrive from the database. then the result will show. now, suppose another user search a record based on same keyword, then the same process will repeat. But my need is,
when user search the record based on keyword, the record will retive from database, and show to user and then it should store as cache in server. if another user search a record based on same keyword, then i have to retive the record from cache of server instead of datebase. i hope it will improve the search module when datebase has huge amounts of datas. please let me know if any other modules in drupal. i hope good responce from your side.

Comments

Comment #1

david strauss

he/him

commented 6 April 2008 at 19:02

Title:	Cacheing Module	» Cache search results
Project:	Drupal.org site moderators	» Drupal core
Version:		» 7.x-dev
Component:	Textual improvements	» search.module
Category:	task	» feature

Moving to the correct queue. Choosing version 7.x-dev because it would be the first place to implement search result caching code. Then, it could be back-ported to run on Drupal.org, possibly.

Comment #2

robertdouglass commented 9 April 2008 at 06:57

There's a flawed patch here: http://drupal.org/node/133902

Caching built nodes would also be a huge boost for search results.

The advcache module has a patch for caching search results in D5: http://drupal.org/node/133902

Comment #3

robertdouglass commented 20 April 2008 at 08:01

Node access is problematic in cases like this. If you cache the administrator's search results you can't show them to anonymous.

Comment #4

david strauss

he/him

commented 21 April 2008 at 15:17

@robertDouglass: We can probably cache using the roles in the key. While that theoretically requires 2^n (where n is the number of roles) as cache entries for each search, the realistic combinations of roles are far more limited.

Comment #5

robertdouglass commented 21 April 2008 at 15:20

David, yes, I've even got a nice function that helps with this in the advcache module. However there are many other types of access controls for nodes that we can't take account of. We'd literally need to cache per user, which is useless. One solution would be to offer caching only when the node_access table is in its original state. That would certainly help a large number of sites (including d.o.)