Hi Willi, a general note: when working with large XML instances, Add will always be slower than Create. If you use the command line, you can specify a directory including all input files, e.g.:
basex create osmdb /path/to/osmdb/files Using REST, you’ll either have to merge the files before running the request, or use multiple add requests (as you are already doing). > JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms512m > -Xmx 1024m -XX:MaxPermSize=512m I’m not sure what’s the particular reason for the failure, but you could try to change -Xmx to a higher or (yes!), smaller value. If that doesn’t help, you may be successful with setting some explicit split values (see [1]). In this case, however, I would recommend you to try the command-line first and set debugging to true. In debugging mode, you will get some hints what values might be promising. Hope this helps, Christian [1] http://docs.basex.org/wiki/Indexes#Index_Construction ___________________________ On Thu, Mar 28, 2013 at 5:29 PM, Willi Firulais <[email protected]> wrote: > Hallo Chirs, > > Thx for your hints - without that would have never come up to that! > > Based on that i've decided to add the following line to the creation script. > This copies over the whole data into a new directory on your application > server and in addition adds the index files > (so check if you have enough space and time ;-) for this operation. > > curl -i -X GET > http://admin:[email protected]:8080/BaseX77-20130321.085136/rest/osmdb?command=OPTIMIZE+ALL > > Currently im gettion an "Out of Main Memory" with the OPTIMAZE+ALL command > when it comes to build the index. > During the OPTIMIZE+ALL the .atv,.tbl,.tbli files have been copied over into > the reorganization directory > successful and then the process dies with the "Out of Main Memory". > > Size of db (as mentioned in thread): > http://127.0.0.1:8080/BaseX77-20130321.085136/rest/osmdb?command=INFO+DB > > ... > Database Properties > Name: osmdb > Size: 7407 MB > Nodes: 355247222 > Documents: 588 > ... > Memory of JVM (JBoss 7.1.1 with only baseX deployed to it): > JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms512m > -Xmx 1024m -XX:MaxPermSize=512m > > best Willi > > P.S.: I realy like this REST interfaces of baseX (simple and powerful) - > great work - keep on going! > > > Mar 28, 2013 07:52:14 AM, [email protected] wrote: > Hi Willi, >> >>> curl -i -X PUT >>> http://admin:[email protected]:8080/BaseX77-20130321.085136/rest/osmdb >>> curl -i -X PUT -T "part1.osm" >>> >>> http://admin:[email protected]:8080/BaseX77-20130321.085136/rest/osmdb/part1.osm >>> curl -i -X PUT -T "part2.osm" >>> >>> http://admin:[email protected]:8080/BaseX77-20130321.085136/rest/osmdb/part2.osm >> >>the attribute index will be discarded when running updates. You can >>either run "optimize" after having performed all updates, or set the >>"updindex" flag to "true". Please check out [1] for more details >> >>> curl -i -X GET >>> >>> http://127.0.0.1:8080/BaseX77-20130321.085136/rest/osmdb?command=CREATE+INDEX+ATTRIBUTE >> >>How much main memory has been assigned to the BaseX JVM, and how large >>is your data? >> >>[1] http://docs.basex.org/wiki/Index#Updates >> _______________________________________________ BaseX-Talk mailing list [email protected] https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
