Re: [basex-talk] Could not reserve enough space for object heap

2017-08-16 Thread Christian Grün
> I am running 64 bit, a x86-x64 JVM so I'd thought I could assign a larger > amount of memory to it. Hm. You could try to specify -d64 to ensure that the 64bit JVM is used. > Why does it need that much memory to just launch? Is it > trying to load some thing of all the existing databases in

Re: [basex-talk] Could not reserve enough space for object heap

2017-08-16 Thread Bram Vanroy
Hi Christian Thanks again for the quick reply. I am running 64 bit, a x86-x64 JVM so I'd thought I could assign a larger amount of memory to it. In any case, I am confused as to what the error message means in a BaseX context. I am simply trying to *start* the basex server, and I

Re: [basex-talk] Could not reserve enough space for object heap

2017-08-16 Thread Christian Grün
Hi Bram, As was indicated before, the JVM is restricted to appr. 1.4 -1.5, sometimes 1.6 GB on 32 bit Windows systems. Generally (and as you have impressively proven), it is indeed possible to have millions of databases in a single BaseX instance. In practice, it is recommendable to find a

Re: [basex-talk] Could not reserve enough space for object heap

2017-08-16 Thread Kirsten, Dirk
Indeed, now I googled this (https://stackoverflow.com/questions/1434779/maximum-java-heap-size-of-a-32-bit-jvm-on-a-64-bit-os) and learned that 32-bit windows is only able to allocate 1.4GB to 1.6GB in practice. I was under the impression that at least 2GB should be usable. So if this is root

Re: [basex-talk] Could not reserve enough space for object heap

2017-08-16 Thread Imsieke, Gerrit, le-tex
It wasn’t clear to me from the OP whether the issue of *slowness* persisted after raising max heap to 2 GB, or whether the issue of *not being able to allocate this amount of space at all* persisted. If Bram set max heap to more than 1.5 GB and immediately received the message “Could not