On 2016-09-30 16:36, Pascal Heus wrote:
Now this is on a AWS EC2 t2.small instance with just ~2Gb or memory. Maybe more memory may solve this issue (?). But in any case concerned that the server hangs without warning or error message in the log. Any potential workaround? Suggestion most appreciated
How many rows are you talking about? t2s are very limited on CPU and I/O bandwidth, they also reduce your CPU power once you've reached your limit. This also comes faster than you'd expect, we used to run into this on small web server from compressing the log files. I find bigger instances (m3s) better for monetdb, especially that being analytic work, we can shut down the instances when not in use, keep the cost to something very reasonable. -- http://yves.zioup.com gpg: 4096R/32B0F416