we have a ibm machine using aix system, can monetdb run on this system?
_______________________________________________
users-list mailing list
users-list(a)monetdb.org
http://mail.monetdb.org/mailman/listinfo/users-list
I work for a company Adclick on Portugal, and we are trying MonetDb and
benchmarking it. We are doing it at AWS (Amazon Web Services), that IO is
very low, so we didn't expect great numbers, but we are very surprised
great numbers appear. Now we will benchmark on server with SSD disks. I'm
really enjoying MonetDb, *very good work *developing team. I think if
MonetDb team work in replication master-slave, on real delete's! more rpm's
for CentOS, AMI to Amazon Cloud, MonetDb can become real a top commercial
product (i already tried so many).
I have a question regarding memory:
"MonetDB excessively uses main memory for processing, but does not require
that all data fit in the available physical memory. To handle dataset that
exceed the available physical memory, MonetDB does not (only) rely on the
available swap space, but (also) uses memory-mapped files to exploit disk
storage beyond the swap space as virtual memory."
"For example, while bulk-loading data (preferably via a COPY INTO
statements from a (possibly compressed) CSV file), MonetDB need to have all
columns of the table that is currently being loaded "active", i.e.,
accessable in the address space. However, during loading, parts of the data
are continuously written to the persisten files on disk, i.e., the whole
table does not have to fit into main memory. E.g., loading a 100 GB table
works fine on a system with 8 GB RAM and 16 GB swap -- provided there is
sufficient free disk space."
Bulk-loading is not a problem since we split CSV in chunks of 2-5M, but i'm
more concern about queries, our datasize will be around 100-150GB ~1B rows
and we are thinking on 32GB Memory server. I think 32GB memory will be more
than enough for any query below:
Our queries will be
select ..., sum(...) where senddate>X and senddate<Y group by K, [Z]
Or
select ..., sum(...) where somecolumn = T and senddate>X and senddate<Y
group by K, [Z]
We will have just one table, and we will have some concurrency, not a lot,
we expect 50-200 (depending on the time of day) queries per minute. So it
can happen 3-5 queries at the same time. MonetDb will be able to handle
this with 32GB of memory without swapping?
I watch http://www.youtube.com/watch?v=yrLd-3lnZ58 and in our cause with
our queries with senddate>X and senddate<Y it looks like that concurrent
queries will not be able to share data between.
Of course i will test concurrency before putting on production, but if i
can get a rough answer will be great. Thanks a lot in advance.
--
*Eduardo Oliveira
* *IT*
***Email:* eduardo.oliveira(a)adclick.pt <nuno.morais(a)adclick.pt> *Web: *
www.adclickint.com <http://www.adclickint.com/>
*
* <http://www.adclickint.com/>
<http://www.adclickint.com/>
_______________________________________________
users-list mailing list
users-list(a)monetdb.org
http://mail.monetdb.org/mailman/listinfo/users-list
Hey there, when I run this
create table dim_date (id integer autoincrement primary key, date date
unique not null);
I get this
syntax error, unexpected IDENT, expecting ')' or ',' in: "create table
dim_date (id integer autoincrement"
Is that expected?
I'm running a compiled version of monet 11.13.3 on a debian machine.
--
Marcelo Lacerda
_______________________________________________
users-list mailing list
users-list(a)monetdb.org
http://mail.monetdb.org/mailman/listinfo/users-list
I'm running MonetDB on Ubuntu 10.04, with Monet built from the
Oct2012_release <http://dev.monetdb.org/hg/MonetDB/rev/3c157ea4be53> tag.
I have a client program that connects using the JDBC driver and issues a
simple SQL query using limit and offset.
I see that:
- limit and offset work when using literal parameters in the SQL string
- limit works by itself when using a bind parameter
- offset works by itself when using a bind parameter
- when specifying both limit and offset and using a bind parameter for
either or both, the merovingian segfaults with a message like this:
database 'click' (2428) was killed by signal SIGSEGV
Examples of queries that work:
SELECT * FROM the_table LIMIT 5 OFFSET 100;
SELECT * FROM the_table LIMIT ?;
SELECT * FROM the_table OFFSET ?;
Example of queries that don't work:
SELECT * FROM the_table LIMIT ? OFFSET ?;
SELECT * FROM the_table LIMIT 5 OFFSET ?;
SELECT * FROM the_table LIMIT ? OFFSET 100;
I've tried passing in the limit and offset as 64 bit integers (long), 32
bit integers (int) and strings, and none of these work.
I also tried downgrading to MonetDB Database Server v1.6 (Jul2012-SP2) but
had the same issue.
Has anyone else run into this? Is this a new bug that I should file?
Thanks,
Percy Wegmann
_______________________________________________
users-list mailing list
users-list(a)monetdb.org
http://mail.monetdb.org/mailman/listinfo/users-list
