Re: Cached ADO
- From: "Anwar Shafiev" <AnwarShafiev@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 30 Jun 2005 03:15:02 -0700
Bill, thanks for the answer.
You are right. Disconnected recordsets can dramatically improve the
performance. But sometimes even this is not enough. Currently, I'm working on
a project, which handles thousands of records in almost real-time conditions.
I made some performance tests with a disconnected ADO recordset on my
P4-3.2GHz with HT, 2Gb RAM, 300 Gb RAID 0. Adding 100,000 records (20 numeric
fields, no BLOBs) into a disconnected recordset takes about 30 seconds.
Flushing takes ten times longer. Our customers have definitely less powerful
computers. Well, I'm pretty sure that at least in-memory operations can be
improved. I'm looking for some kind of very fast caching layer between ADO
and my application. I tried to find something available on the market, but
didn't find anything. Recently, I have started writing my own caching layer.
It already supports some basic operations like navigation, simple indexed
searching, and data manipulation. Performance tests have shown that adding *2
millions* of records *with* BLOBs takes about 3 seconds on my machine. On the
other hand, I understand that writing such a layer with a full ADO
functionality will take some time, and I would prefer to buy a solution,
which is already available, rather than writing my own, and maybe
re-inventing a wheel.
Anwar
"William (Bill) Vaughn" wrote:
> What are you trying to do? ADO classic (and ADO.NET) both support
> disconnected (cached if you will) Recordsets (and DataSets).
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
>
> "Anwar Shafiev" <Anwar Shafiev@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C1C1F32B-30A0-4E01-B25A-FE8113635F0C@xxxxxxxxxxxxxxxx
> > Hello everyone,
> >
> > Does anyone know any libraries (free or commercial) to cache classic ADO
> > recordsets? Actually, it was already implemented in ADO.NET, thus having a
> > database in memory. Is there anything similar to it, but not a .NET based
> > solution, working with ADO and C++ on Win32 platform?
> >
> > Thanks,
> > Anwar
> >
>
>
>
.
- References:
- Cached ADO
- From: Anwar Shafiev
- Re: Cached ADO
- From: William \(Bill\) Vaughn
- Cached ADO
- Prev by Date: Re: HOW DO I EDIT A RECORD IN ADO
- Next by Date: Add values to DataGridViewRow "manually" -> Rows are empty
- Previous by thread: Re: Cached ADO
- Next by thread: Re: Cached ADO
- Index(es):
Relevant Pages
|
|