Re: [MonetDB-users] result cache?

Hi, Jennie, Our main table has around 200M rows with 18 columns, and increasing 1.5M rows daily. Right now it's occupying 24G disk spaces. We are pretty interested in develop a result cache by our own, any hints could you give us? Thanks Allen -----Original Message----- From: Ying Zhang [mailto:Y.Zhang@cwi.nl] Sent: Sunday, July 26, 2009 6:08 AM To: Communication channel for MonetDB users Cc: Martin.Kersten@cwi.nl Subject: Re: [MonetDB-users] result cache? On Jul 24, 2009, at 20:32 , Allen Zhang wrote:

Thanks a lot, we will try to get into monventure if recycler does not recycle our whole database.

Hello Allen, Just out of curiosity: how large is your database? Regards, Jennie

On 7/24/09 11:22 AM, "Martin Kersten" wrote:

...

Allen Zhang wrote:

...

Martin,

Thanks, for our situation, we have no control of the client behave (we know, that's bad), so the result cache in the database side that will really help.

Does monetdb support materialized view? Or can we use the recycler to help get around this? It is cheap to store the result of a query into a table.

If you adventurous, you can download the development version and enable the recycler pipeline. No guarantees ;)

...

Best Regards Allen

On 7/24/09 10:49 AM, "Martin Kersten" wrote:

...

Allen Zhang wrote:

...

Thanks Milena,

Is that means monetdb does not provide final result cache? The result set is fully materialized and delivered to the interface API. Re-use of that particular result set is the responsibility to the client software.

...

We have sql client will query same query to the database multiple times, imaging each query took 2 minutes to run, that's will be really painful when the client ask 10 times, since our database is readonly, so a real result cache will really help us. I would consider it an application design error if a client application issues the same request over and over again.

For this, materialized views have been invented and even temporary tables are often used to cope keep expensive results around.

Alternatively, database triggers are used to react to changes in the underlying tables.

MonetDB has a query cache, which means it will analyse a query once and will reuse the plan whenever possible. And, indeed, the development code contains a recycler, which avoid duplicate work from different users. Provided, it is beneficial to do so.

regards, Martin

...

Regards Allen

------------------------------------------------------------------------

...

...

...

...

-----

...

...

...

...

...

...

...

...

...

...

_______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users

----

...

...

...

-- _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users

------------------------------------------------------------------------ ------

_______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users

------------------------------------------------------------------------ ------ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users