Hi Sebastian,
given your brief description of the problem, I don't expect that MonetDB itself triggers/causes the problem, but rather suspect that it is related to the system you're running on.
If I understand you correctly, your machine has ample CPU and RAM resources to execute your queries, right?
Are you running a single query / client at a time, or are multiple queries / clients active concurrently?
Can / did you monitor the system behavior/activity during the "hick-ups"? E.g., are there other ("heavy") processes running? Is there (unexpected) I/O activity? Is there unexpectedly high CPU system (rather than user) load?
Please also see the experiences shared at in this blog post: http://engineering.linkedin.com/performance/optimizing-linux-memory-manageme... and this monetdb user mailing list thread: https://www.monetdb.org/pipermail/users-list/2013-December/thread.html#7024
Best, Stefan
----- Original Message -----
HI,
We are using monetdb for some statistical analysis.
The queries are very fast (0.2 sec), but some times (not regularly) the queries get peeks of up to 32 sec for the same query.
CPU and RAM don't change and are way higher than actually needed.
Does any one have this same situation? Any idea what could be doing this?
Best regards and thanks to any help.
sebastian
developers-list mailing list developers-list@monetdb.org https://www.monetdb.org/mailman/listinfo/developers-list