Hi all,
I've run into a behaviour that I would like to understand and possibly
disable.
Two times per day the mserver daeomon starts trashing the disk
furiously, I see that the size on disk of data directory goes up to 115
GB from 85 GB and then comes back again to the same initial size, during
this process disk utilization goes trough the roof. Can anyone tell me
what is monetdb doing? There are no import/export process running at
this times, it seems that monetdb is doing some kind of data
compaction... is there anyway to disable this?
$ mserver5 --version
MonetDB 5 server v11.15.7 "Feb2013-SP2" (64-bit, 64-bit oids)
Thanks!
--
Luis Neves
Hai Bas,
We hebben vandaag een probleem met substring gefixed die waarschijnlijk met jou probleem te maken heeft. Zou je misschien willen kijken of die fix iets voor je doet? We kunnen dat helaas zelf niet testen.
Mvg, Jennie
On Jan 27, 2014, at 15:02, Ying Zhang <ying.zhang(a)monetdb.com> wrote:
> Hai Bas,
>
> Thanks again for the information. I was hoping that with some luck your problems might be gone in RC2 due to various fixes, unfortunately they are not. I'd like to look more deeply into the problems you have reported. Problems like not effective updates are rather show stoppers.
>
> Would you please provide me the ASC files with which the problems can be reproduced? You can send the files directly to me if necessary. Thanks!
>
> Regards,
>
> Jennie
>
> On Jan 27, 2014, at 13:05, Bas Kaptijn <b.kaptijn(a)chs.nl> wrote:
>
>> Tested with Jan 2014 RC2. All mentioned problems still occur with this release.
>>
>> Also, with the no_mitosis_pipe my program has problems with DELETE’s and possibly other queries
>> not taking place effectively somehow. For me the investigation of the Jan2014 build stops here
>> until some of the problems mentioned here are fixed
>>
>> Regards, Bas
>>
>> Van: Bas Kaptijn
>> Verzonden: dinsdag 21 januari 2014 12:55
>> Aan: 'users-list(a)monetdb.org'
>> Onderwerp: RE: problem with Jan2014 build
>>
>> Some last info: the problem disappears when using the no_mitosis_pipe optimizer pipeline.
>>
>> sql>set optimizer='no_mitosis_pipe';
>> operation successful (0.139ms)
>> sql>SELECT * FROM source1 WHERE SUBSTRING(SOURCE,1,2)='04' LIMIT 1 OFFSET 400000;
>> +-----------------------------------------------------------------------------+--------+----------------------------------------------------------------------------------------------------------------------------------------------------+
>> | file | line | source |
>> +=============================================================================+========+====================================================================================================================================================+
>> | /home/bkaptijn/DDDB/.tmpinputdir/9772_9999_20130501_20130531_Schade_516.ASC | 430664 | 04999999999999999999999999999999999999999
>> :
>> +-----------------------------------------------------------------------------+--------+----------------------------------------------------------------------------------------------------------------------------------------------------+
>> 1 tuple (1.1s)
>> sql>set optimizer='default_pipe';
>> operation successful (0.305ms)
>> sql>SELECT * FROM source1 WHERE SUBSTRING(SOURCE,1,2)='04' LIMIT 1 OFFSET 400000;
>> +------+------+--------+
>> | file | line | source |
>> +======+======+========+
>> +------+------+--------+
>> 0 tuples (798.870ms)
>>
>> Regards, Bas
>> _______________________________________________
>> users-list mailing list
>> users-list(a)monetdb.org
>> https://www.monetdb.org/mailman/listinfo/users-list
>
Hi,
What is the recommended way to work with dynamic queries, any optimization
techniques, is there a way to avoid them using functions written in MAL.
Tested with Jan 2014 RC2. All mentioned problems still occur with this release.
Also, with the no_mitosis_pipe my program has problems with DELETE's and possibly other queries
not taking place effectively somehow. For me the investigation of the Jan2014 build stops here
until some of the problems mentioned here are fixed
Regards, Bas
Van: Bas Kaptijn
Verzonden: dinsdag 21 januari 2014 12:55
Aan: 'users-list(a)monetdb.org'
Onderwerp: RE: problem with Jan2014 build
Some last info: the problem disappears when using the no_mitosis_pipe optimizer pipeline.
sql>set optimizer='no_mitosis_pipe';
operation successful (0.139ms)
sql>SELECT * FROM source1 WHERE SUBSTRING(SOURCE,1,2)='04' LIMIT 1 OFFSET 400000;
+-----------------------------------------------------------------------------+--------+----------------------------------------------------------------------------------------------------------------------------------------------------+
| file | line | source |
+=============================================================================+========+====================================================================================================================================================+
| /home/bkaptijn/DDDB/.tmpinputdir/9772_9999_20130501_20130531_Schade_516.ASC | 430664 | 04999999999999999999999999999999999999999
:
+-----------------------------------------------------------------------------+--------+----------------------------------------------------------------------------------------------------------------------------------------------------+
1 tuple (1.1s)
sql>set optimizer='default_pipe';
operation successful (0.305ms)
sql>SELECT * FROM source1 WHERE SUBSTRING(SOURCE,1,2)='04' LIMIT 1 OFFSET 400000;
+------+------+--------+
| file | line | source |
+======+======+========+
+------+------+--------+
0 tuples (798.870ms)
Regards, Bas
The MonetDB team at CWI/MonetDB BV is pleased to announce a second
release candidate for the upcoming Jan2014 feature release.
Many things have changed in this release compared to the previous
(Feb2013) release (that's why it took so long). For a smooth upgrade I
would urge you to try out this release candidate and to provide feedback
on our bug tracker (http://bugs.monetdb.org).
A number of bugs in the previous release candidate have been fixed.
Among others, packaging errors on Debian and Ubuntu have been fixed, and
a problem with slow startup has been fixed.
The release candidate can be found at
http://dev.monetdb.org/downloads/testing.
--
Sjoerd Mullender
Hello Jennie,
I can to do clustering, to use (map-reduce, handoop) as monetdb for large
amounts of information? any have any documentation for this?
What amount of information are you talking about?
I have two applications. In 1 i have over 100.000.000 millions of records.
And i have other application as more of 400.000.000 millions of records and
i need migrate this of oracle.
Thanks,
Edgar M
Hello,
We have just started using MonetDB in production and can I start by saying its a pretty impressive database. We are having a problem with query when we have 4 -5 users running reports and I wanted to know if anyone could recommend some optimisation tips. On particular one is multiplex-funnels. I can't find any documentation on how to create it. I read some where that it can be used to replicate data between two servers. It would be great to get some guidance on how to do this.
Kind Regards
Dear all,
I am using MonetDB for 64 bit Windows from the package MonetDB5-SQL-Installer-x86_64-20131120.msi.
If I compile the example mapi program from here http://www.monetdb.org/Documentation/Manuals/SQLreference/Programming/MAPI and cause an error in a query (e.g. incorrect port number in mapi_connect params) then the application will crash with the following message:
0xC0000005: Access violation writing location 0x0000000000000024
This appears to happen if any of the following functions are called:
mapi_explain(dbh, stderr);
mapi_explain_query(hdl, stderr);
mapi_explain_result(hdl, stderr);
The same code works correctly on Ubuntu 13.04 with MonetDB-11.15.17?.
Can anyone reproduce this error on Windows?
Best regards and thanks,
Alastair
Hi all,
I am writing a simple C++ dll which uses the mapi interface to connect to MonetDB.
The query itself runs extremely fast which is fantastic. I did notice that the mapi_connect() takes approximately 1 second to connect on my machine on a local socket.
Is there anyway to improve this connection latency? I can't unfortunately use a connection pool or keep the connection open due to the design of the calling application.
Best regards,
Matthew Russell