On Mon, May 17, 2010 at 09:27:41AM -0400, dariuszs wrote:
Hi, Then how is that different than using MySQL memory tables - it's not.
It's totally different. It's not comparable at all. For details see the related research paper: http://repository.cwi.nl/search/fullrecord.php?publnr=14287 Stefan
Dariusz.
Roberto Cornacchia wrote:
KA-BUM! :-)
..sorry, I couldn't resist this. Seriously, my first reaction would be: well, if you overload the system, you get what you can expect - a slow system. MonetDB is not scared of working out of physical memory, but it can't do magic. It all depends of course on the real DB usage. I guess it is not realistic to think that all users would use the same tables at the same time, which would worsen the situation of course. One of the optimizers under development (recycler) aims at making intermediate results reusable - also across different sessions. With this in place, you could expect massive improvements in a scenario with many users firing similar queries.
Roberto
On Mon, 2010-05-17 at 08:50 -0400, dariuszs wrote:
Hi, So what happens (performance wise) when you have 50GB of memory, 300GB of data and on average 100 concurrent users using all the tables and columns in your database? Thanks. Dariusz.
------------------------------------------------------------------------------
_______________________________________________ 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
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4199 |