Best background refresh strategy
Hi,
No changes done to the basic setup.
I'm running OLAP queries and not all 54 columns are used in any query, it depends on the query which columns are used.
The query is kind of SELECT SUM(),AVG(), SUM() + WHERE + GROUP BY
The WHERE columns have a great compression so it's faster to find by them.
My last test runs in 340 ms and aggregates between 900 and 2000 rows per result.
Care: "select * from table where key = 123456" (not an expert but this is pure OLTP)
Same for me, "select * from bigcalendar limit 2" -> Sometimes I have to kill it, :) but it's something that I don't need at all.
I'm using MonetDB as a kind of cache of my OLTP system.
IMO MonetDB is perfect for OLAP (not only analytical, operational as well! Now I'm working on the refresh approach)
if you are looking for a fast search engine by key, maybe a pure key/value-store is more appropriate.
Hope this helps.
Gustavo Brian
Developer
-----Original Message-----
From: users-list [mailto:users-list-bounces+gustavo.brian=sunhotels.net@monetdb.org] On Behalf Of users-list-request@monetdb.org
Sent: martes, 27 de enero de 2015 12:00
To: users-list@monetdb.org
Subject: users-list Digest, Vol 29, Issue 20
Send users-list mailing list submissions to
users-list@monetdb.org
To subscribe or unsubscribe via the World Wide Web, visit
https://www.monetdb.org/mailman/listinfo/users-list
or, via email, send a message with subject or body 'help' to
users-list-request@monetdb.org
You can reach the person managing the list at
users-list-owner@monetdb.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of users-list digest..."
Today's Topics:
1. Re: Best background refresh strategy (shamsul hassan)
2. Join index structure (Joseph D'silva)
----------------------------------------------------------------------
Message: 1
Date: Mon, 26 Jan 2015 11:44:49 +0000
From: shamsul hassan
On 25/01/15 06:48, Gustavo Brian wrote:
Hi,
Hi,
thanks for the interest and appraisal.
I'm trying monetdb as a bigtable for calendar based queries. I've created a 338 million rows / 54 columns table and ran queries in ms. That's perfect! I wonder to see if monetdb is suitable for a search service with high traffic (several hundred request per second) and which will the best data update strategy because during the "updates/insert/copy into" actions everything gets blocked.
Queries should not be a problem, but for updates you should read and understand https://www.monetdb.org/blog/monetdb-sql-transaction-management-scheme https://www.monetdb.org/Documentation/Manuals/SQLreference/Transaction s
I would like to know how cluster mode will help as well.
Depends on the complexity of the query and your machine specs. regards, Martin
Thanks, Gustavo Brian _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
participants (1)
-
Gustavo Brian