hi, monetdb has always held ram after completing an operation on windows. my solution has always been to simply close and re-open mserver. hannes is now working on monetdblite, which if successful is going to attract lots of new users who aren't going to know that they need to close & re-open the server after any big operation. i have uploaded a video to youtube detailing this problem. it just shows the same csv being imported ten times into ten distinct tables. each time the ram monitor ticks up 0.3gb and never comes back down. the entire operation holds 3gb of ram. https://youtu.be/X8fOSFplVh0 i have also filed this bug report. https://www.monetdb.org/bugzilla/show_bug.cgi?id=3835 thanks! On Tue, Aug 4, 2015 at 9:21 PM, Anthony Damico wrote:

hi, this is just a general request for the awesome folks at cwi: could you give some serious thought to optimizing ram usage on windows? this happens to me a lot, i end up just leaving these big joins to run overnight--

http://s30.postimg.org/saeo9ca7l/overloaded.png

happy to write up some r-driven reproducible examples if there's willingness to combat these bottlenecks. thanks as always from your biggest fan.