records returned number about 5000. NO ONE is going to page through all
5000 records. This is what the search filters are for. Just return the top
20, 50, 100 records ordered by whatever your business rules require ONLY IF
there is no search criteria entered. IF there is search criteria entered,
then you can return a varied result set based on the entered criteria.
Caching 5000 records in an indeterminate amount of sessions is not a good
idea. Furthermore, caching in the application scope would keep wiping out
the cached query, unless every user is searching for the same exact critera
(highly unlikely).
Another idea using the application scope would be to cache the full 5000
records and then use query of query for specific searches, which you
wouldn't cache as they'd be narrowed down by the user-entered criteria.
Andy
-----Original Message-----
From: Micha Schopman [mailto:[EMAIL PROTECTED]
Sent: Friday, July 30, 2004 8:48 AM
To: CF-Talk
Subject: RE: The search is killing the server. Please help!
This means if you have 10.000 users doing a search for "dog" the server
now creates 10.000 session entries each with the exact same resultset
for dog ;)
That is why I suggested application variables. Everybody has instant
access to the cache if they search for the same thing.
Micha Schopman
Software Engineer
Modern Media, Databankweg 12 M, 3821 AL Amersfoort
Tel 033-4535377, Fax 033-4535388
KvK Amersfoort 39081679, Rabo 39.48.05.380
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
