Re: interMedia 8.1.6 performance problem

I am newby in all this, but in case you are using JDBC you should definitely check the new JDBC 2.0 features, one of which is "Result set enhancements" .
Try here:

http://oradoc.photo.net/ora816/java.816/a81354/resltset.htm#1000888

In article <%Ltd5.232$5l.95198_at_news.pacbell.net>,   "Charlie Toohey" <toohey_at_ix.netcom.com> wrote:
> I'm using interMedia for a Web based Search engine and display the
 result
> set in groups of web pages (15 or whatever result hits per page).
>
> The problem is that my Web application does not have any persistent
 data
> storage between pages (other than passed query string parameters), so,
 when
> the user wants to see the next set of results, I have to run the same
> interMedia query all over again. I've tried storing the results in a
 table,
> but have potentially hundreds of users searching at the same time ---
 this
> creates problems with latch contention -- since I am constantly
 updating and
> reading from the same blocks of the table, Oracle has to create and
 maintain
> many, many copies of the same block -- this is not a scaleable
 solution and
> with more and more users searching simultaneously every day, this is
 not an
> option.
>
> I was considering creating a temp table per user when the user begins
 a
> session on my site -- so each user would have their own results table,
> eliminating any possibilties of contention. This temp table would only
 exist
> for the duration of the users session and would be used to store a
> particular users search results. The user could then page thru the
 search
> results, sort them, or whatever and I would only have to conduct an
> interMedia search one time. Whenever the user enters a new search
 term, the
> table would be truncated and the new search results written.
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Thu Jul 20 2000 - 00:00:00 CDT